First use
Set up the commute that matters.
Home, work, walking preference, and accessibility needs stay focused on route quality.
Home
Work
Step-free routes
Continue
Back to design catalog
GenerateMobile app · Transit
Catalog study 10
Commuter mobile journey
A touch-first transit experience that guides a commuter from first-use preferences into route planning, disruption awareness, and a confident arrival state.
Repository-owned synthetic study. It proves composition and design reasoning without claiming live product behavior, customer adoption, measured outcomes, or production acceptance.
Primary task
Know the route. Keep moving.
The experience moves from a short preference setup into one route decision, visible service context, live trip progress, and recovery states that do not hide the next action.
Morning commute
Central → Senayan
28 minOn time
Walk to Central4 min
MRT Northbound16 min
Walk to office8 min
HomeTripsSavedProfile
Service change
Platform moved to track 2
Arrival remains 08:42. The alternative route is one action away.
Offline
Last route remains available with a clear stale-data label.
Arrival
You made it.
08:41 · one minute early
Loading
Skeleton route rows preserve the decision layout.
Ready
Route, duration, service status, and action are visible together.
Error
Cause and recovery action appear without deleting the current trip.
Success
Arrival confirmation closes the task without a celebratory modal.
Proof details
Starting brief
Create a mobile transit companion for daily commuters who need fast route decisions, visible service changes, and calm recovery when a journey is disrupted.
Synthetic mobile product study. Routes, times, service alerts, account state, GPS, ticketing, and live transit data are not connected to production services.
Primary task
Choose destination → compare route → track trip
Navigation
Home · Trips · Saved · Profile
States
Loading · ready · disruption · offline · arrival
Touch
Large targets, bottom reach, status beyond color
Result
A compact mobile product system with short onboarding, one dominant route action, persistent trip status, bottom navigation, and explicit loading, success, offline, and service-error states.
Refuses
- Long feature-tour onboarding
- Map-first screen without a decision hierarchy
- Tiny controls or color-only service status
Related catalog work
More product interfaces, systems, and quality proof.
Product interfaces · RefineOperations dashboard refinementDesign systems · ImplementRepository-native component systemTransformation · ReviewResponsive interface acceptance reviewProduct interfaces · RefineSaaS analytics workspaceDesign systems · ImplementMulti-surface interface systemTransformation · RefineLegacy SaaS interface refinementTransformation · AuditMobile commerce audit and correctionTransformation · RedesignBrand experience redesign and review