Mobile app design built around how people actually hold a phone

An app is a sequence, not a gallery. The work starts by mapping the paths a user takes — first launch, the main job they came to do, the recovery path when something goes wrong — before any screen gets visual design.

Mapping first is what surfaces the screens nobody remembered to ask for: the empty state, the expired session, the half-finished form someone came back to three days later.

iOS and Android users have different muscle memory for navigation, back behaviour and system controls. Designing one screen and shipping it to both platforms produces an app that feels slightly wrong on each.

Where a shared design language makes sense, it is kept shared. Where the platform expects its own pattern, the design follows the platform.

The deliverable is a clickable Figma prototype, not a slide of screens. That is what makes it possible to hand your phone to five people and watch where they hesitate, while changing the answer still costs a Figma edit rather than a sprint.

The same prototype is what developers use to understand intent — transitions, states and what happens on tap are demonstrated rather than described in a comment.