A product direction built around a complete journey.
A map-first mobility simulation covering destination search, route options, pickup, matching, trip status, safety, history, transit, and wallet. The case study exposes the project’s structure and delivery boundaries so visitors can assess the visual system, route coverage, and intended interactions without mistaking a concept for commissioned client work.
01
Multimodal rides and transit alternatives
The route architecture is organised around multimodal rides and transit alternatives, with each named screen assigned a specific interaction role.
02
Project-specific visual direction
Accessible blue and cream with luminous paths, bottom-sheet choreography, unambiguous trip states, and softly layered maps.
03
Original asset plan
Original map tiles and route SVGs, fictional drivers and trips, generated vehicle artwork, and local-only payment fixtures.
02 · Experience architecture
Navigate the complete app map.
Every named screen opens directly, making the concept’s scope inspectable and shareable without loading every experience route on this page.
20Connected screens
Routes describe the frontend experience. A visible route does not by itself claim a live backend integration or native store release.
03 · Evidence and boundaries
Original presentation, documented provenance.
Reference research and implementation status are stated separately. Third-party screenshots, logos, and branded assets are not used in this presentation.
Reviewed Mobbin evidence
Reference record
The links below were supplied as reviewed Mobbin reference records for pattern research. They do not imply affiliation, endorsement, or permission to republish source screens.
Asset record: Original map tiles and route SVGs, fictional drivers and trips, generated vehicle artwork, and local-only payment fixtures. Reference imagery is research-only. Public experiences ship original or licensed assets with source records.