External Client Apps are V2 of Connected Apps: the framework that lets an outside application integrate with a Salesforce org using APIs and standard protocols like SAML, OAuth, and OpenID Connect. I designed a single, connected experience that gives admins and developers one place to create these apps, deployed locally by default.
An External Client App is an application that can be developed on (or installed into) a Salesforce org. It represents an inbound connection to an external service. A few examples:
Part of my job was making a deeply technical concept legible. Here, in plain terms.
Managing a Connected App required developers to navigate two separate areas of Setup with no path between them. So I mapped the existing journey end to end, screen by screen. The fragmentation isn't a claim. It's something you can see.
Same goal. Two destinations.
To reach the developer side, users abandon the first workflow and start over in a completely different area of Setup.
Finally reaches the destination.
The same surface, the same app (Test App), shown under two different page titles. You can’t tell where you are.
One task, many destinations.
Developers weren’t struggling with Connected Apps. They were struggling to understand where the product lived.
A new experience that's clear and quick for developers, admins, and customers to install, create, manage, view, or even package as an app.
Stand up an external client app from one guided place.
Every app in one sortable, searchable home.
Tune OAuth policies and Trusted IP Ranges inline.
Bundle and distribute it as a managed app.
One connected lifecycle, instead of a tangle of disconnected screens. The real screens for each step are below.
Went deep on a dense, technical domain: trainings and documentation on Connected Apps, hands-on time in a sandbox org, and user-flow mapping to surface the gaps and pain points, capped with a design brief built alongside the PM.
Ran a Setup audit to find common patterns and reusable components, built a new help component, and reused existing ones (table badges, the Custom Attributes flow). Pressure-tested designs through Slack feedback channels, Design Crit, and Demo Days.
As an ambassador for our design system, I pushed to build from the component library and only created custom components when truly necessary, taking those to Accessibility office hours for review.
Created design decks for release planning and handed off in Figma with inspect mode, holding weekly UX meetings to negotiate technical feasibility and looping CX in for labels and descriptions.
The MVP brought the whole lifecycle into one coherent surface, including the flow for editing a Trusted IP Range, where developers tune the OAuth policies that govern how an app connects.
External Client Apps shipped as the platform-wide replacement for Connected Apps. It's now the required framework for every new Salesforce integration, so the create, manage, and migrate experience I designed is the path every developer and admin building on the platform goes through.