A product direction built around a complete journey.
An evening-culture app spanning discovery, events, venues, slots, ticket options, checkout, wallet, calendar, artists, guides, and history. 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
Local culture discovery and ticket wallet
The route architecture is organised around local culture discovery and ticket wallet, with each named screen assigned a specific interaction role.
02
Project-specific visual direction
Deep violet and lantern orange with expressive original event art, focused ticket surfaces, and ticket-fold transitions.
03
Original asset plan
Original event posters, fictional venues and artists, CSS QR-like decorative codes not valid tickets, and licensed ambience imagery.
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 event posters, fictional venues and artists, CSS QR-like decorative codes not valid tickets, and licensed ambience imagery. Reference imagery is research-only. Public experiences ship original or licensed assets with source records.