Night Transit
Cobalt night, acid wayfinding and modular motion translate Berlin after dark into a legible product system.
One identity and a complete participant product contract: foundations, components, patterns, navigation, states, journeys, direct pages, accessibility, and portability.
The Match / Quest wordmark stands alone in product chrome. The two-pin heart appears only as a dark symbol on the acid app icon.
No alternative themes remain. Cobalt night carries the system; acid and signal pink identify direction and action.
Cobalt night, acid wayfinding and modular motion translate Berlin after dark into a legible product system.
Compressed display type and coded labels create energy; body text stays quiet around consequence.
Meet face to face, not in a feed
What comes next
Thoughtfully hosted evenings where conversation comes first and every post-event choice remains private.
Friday · Kreuzberg · 19:30
Controls keep a 44px minimum target, visible focus, explicit hierarchy, native semantics, and no color-only state.
Objects carry identity, status, authority, context, and one valid next action; they are never interchangeable generic cards.
Lea WinterKreuzberg
Sophie WeberNeukölln
Mara KleinWedding
Jonas MalikFriedrichshainRepeated semantic workflows are owned once and composed differently for participant phone and desktop contexts.

One private choice; a reveal only when it is mutual.
Confirmed, waitlisted, and attended places stay reachable from Home.
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Owned pattern · responsive · keyboard specified
Ten canonical states cover waiting, absence, interruption, authority, consequence, and recovery.
Known information remains while authoritative details refresh.
The reason and next useful path stay visible.
Current state is refreshed before a safe retry.
Saved details and drafts remain; mutation waits.
The resulting object and next action are ready.
Authority, impact, confirmation, and recovery are explicit.
Mobile and desktop share state and intent while composing navigation and work for their context.
Nine connected stages expose every necessary participant function without requiring the legacy page structure.
Public proposition, event search, filters, save, organizer context
Register, verify, sign in, recover, resume intended task
Profile wizard, photos, phone, preferences, public preview
Free or paid checkout, waitlist, 3DS, cancellation and refund terms
Ticket wallet, QR, manual code, check-in and offline fallback
Eligible co-attendees, private like/pass, draft, deadline and retry
Pending and mutual state, shared event, compatibility context
Mutual conversation, reconnect, files, report and block
Notifications, security, privacy, GDPR, subscriptions and appeals
Every customer-facing feature family is assigned to concrete Night Transit screens and explicit system states; participant areas are the current parity priority.
Landing, public information, localization, consent, legal, contact, newsletter, PWA, and offline.
Registration, sign-in, verification, recovery, session expiry, applications, and role switching.
Wizard, photos, phone, preferences, personality, public profile, validation, and visibility.
Ticket lifecycle, QR, manual check-in, event-scoped outcomes, and offline fallback.
Eligibility, feedback, privacy, deadlines, compatibility, pending choices, and mutual matches.
Mutual chat, realtime states, attachments, report, block, unblock, and appeals.
Home, activity, notifications, settings, security, GDPR, subscription context, and status states.
Application, payout, events, publishing, media, live operations, analytics, and revenue.
Venue directory, details, places, direct requests, proposals, interests, and organizer trust.
Onboarding, inventory, availability, blocked dates, booking decisions, calendar, payout, and revenue.
Canonical agreement, negotiation, relationship-scoped chat, audit history, and handoff.
The original public, access, and participant surface plus focused person and thread drill-downs resolve to static Night Transit entry points.
Accessibility, localization, no-network honesty, portability, ownership, and automated route coverage are part of the system—not post-design cleanup.
Landmarks, labels, visible focus, 44px targets, keyboard completion, reduced motion, and no color-only meaning.
Expansion-safe composition, deterministic dates and money, and localized state or action semantics.
No production API calls, remote assets, or mock success after an error.
Serializable view models, semantic intents, JSON tokens, and framework-independent lifecycle rules.