Completely reimagining how Alexa customers use the Alexa Mobile App by redesigning its core experience from the ground up to be agent-forward, centering around Alexa+.
Alexa+ is Amazon's rebuilt conversational assistant, and the mobile app is how most people reach it when they aren't standing next to an Echo. Through 2025 I was visual design lead on rebuilding the app's core experience around it.
The goal: Alexa+ within arm's reach of every customer, wherever they are. That set a real constraint: if the assistant is the point, it can't be something you navigate to.
We were after three things. Alexa had to be the best mobile AI assistant, not just a good one. The app had to be something people liked using, with distinct experiences for smart home and non-smart-home customers, a near-even split of the base.
And it had to get simpler. The home screen we inherited carried For You, Favorites, Recent Chats, Discovery and its own navigation layer, all competing with the one interaction we wanted first.
FIG_01 — The home screen before and after
This built on the year before, when I helped lead design for the new conversational Alexa in the mobile app, so the redesign started with a point of view on how a conversation should behave on a phone.
The timeline was too aggressive for designing finished screens and working out the pieces afterward, so I inverted the order and started from the components.
I led the design of every new and updated component, and built a custom component library and core UX spec from scratch. Library first meant design and engineering could work in parallel from one source, instead of engineering waiting on finished layouts.
FIG_02 — Core components from the library
I specced each component straight from the library using Figma's Dev Mode, annotations and variables, covering every variant and nested component. A separate spec document would have drifted, and on this timeline things changed weekly.
The redesigned app is agent-forward: you land on Alexa+ instead of going to find it. Front-loading the library and specs is the decision I'd make again; it kept a large team consistent while the design was still moving.