Context
Mobile Flows brief
Start with a clear brief and the source material this Mobile Flows workflow needs.
CONNECTED MOBILE JOURNEYS
Plan every screen before development begins
Arrange complete mobile journeys, compare interaction states, and review the flow in realistic device frames before handoff.
Prototype flow
Connected flowEntry
Action
Result
Journey map
Every screen in context
Follow linked device frames from entry through completion while decisions remain visible beside each screen.
Example workspace
Mobile Flows
Follow linked device frames from entry through completion while decisions remain visible beside each screen.
Method
Working method
Follow linked device frames from entry through completion while decisions remain visible beside each screen.
Review
Review handoff
Keep decisions visible before moving Mobile Flows work into delivery.
State logic
Interaction states that connect
Define taps, transitions, empty views, and recovery paths as one continuous mobile experience.
- 01
Mobile flow planning
Follow linked device frames from entry through completion while decisions remain visible beside each screen.
- 02
Screen concept boards
Define taps, transitions, empty views, and recovery paths as one continuous mobile experience.
- 03
Interaction state edits
Compare compact and expanded displays without losing the intended hierarchy or touch targets.
- 04
Device walkthrough refs
Share annotated flows, component states, and navigation rules in a package developers can inspect.
Device review
Review on real devices
Compare compact and expanded displays without losing the intended hierarchy or touch targets.
| Option | Best fit | Review point |
|---|---|---|
| Mobile flow planning | Follow linked device frames from entry through completion while decisions remain visible beside each screen. | Structure and clarity |
| Screen concept boards | Define taps, transitions, empty views, and recovery paths as one continuous mobile experience. | Output and control |
| Interaction state edits | Compare compact and expanded displays without losing the intended hierarchy or touch targets. | Structure and clarity |
| Device walkthrough refs | Share annotated flows, component states, and navigation rules in a package developers can inspect. | Output and control |
Handoff package
A cleaner product handoff
Share annotated flows, component states, and navigation rules in a package developers can inspect.
Mobile flow planning
Follow linked device frames from entry through completion while decisions remain visible beside each screen.
Screen concept boards
Define taps, transitions, empty views, and recovery paths as one continuous mobile experience.
Interaction state edits
Compare compact and expanded displays without losing the intended hierarchy or touch targets.
Device walkthrough refs
Share annotated flows, component states, and navigation rules in a package developers can inspect.
Release planning
Map the next release
Turn the next feature brief into a connected journey ready for team review.