Skip to case study
All portfolio workApp concept · Collaborative travelOpen experience
Independent concept projectCollaborative travelReference measured · review required

Atlas Thread

A collaborative journey planner joining destinations, day plans, places, maps, bookings, costs, contributors, chat, documents, and offline access.

Launch interactive experience Browse all 20 screens
Project type
Independent concept
Format
Browser-based app
Experience scope
20 connected screens
Industry
Collaborative travel
Fidelity status
Reference measured · review required
01 · Design rationale

A product direction built around a complete journey.

A collaborative journey planner joining destinations, day plans, places, maps, bookings, costs, contributors, chat, documents, and offline access. 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.

  1. 01

    Shared itinerary planning and trip coordination

    The route architecture is organised around shared itinerary planning and trip coordination, with each named screen assigned a specific interaction role.

  2. 02

    Project-specific visual direction

    Folded-map ultramarine and apricot with animated day threads, paper layers, pin clusters, and contributor annotations.

  3. 03

    Original asset plan

    Original illustrated maps, licensed destination-neutral imagery, fictional bookings and expenses, and CSS route threads.

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.

Wise reference study

Reference record

The Wise links below document private clean-room measurement. They do not imply affiliation, endorsement, human approval, or permission to republish source screens.

System
A11 · ios
Studied
2026-08-13
Entry family
wise-trip-entry
Status
reference-measured · human review required

Automated targets: structural changed pixels ≤ 2.0%, full changed pixels ≤ 8.0%, MAE ≤ 0.015, RMSE ≤ 0.035. These are measurement targets, not pixel-perfect certification.

Asset record: Original illustrated maps, licensed destination-neutral imagery, fictional bookings and expenses, and CSS route threads. Reference imagery is research-only. Public experiences ship original or licensed assets with source records.

  • Wise primary screen

    balance header, compact action chips, horizontal account cards, and transaction list

    • Twelve-pixel page gutters frame balances and transactions
    • Send, add, and request actions are compact 34 px pills
  • Wise alternate state

    account paging changes ledger context while transfer and calculator flows preserve entered values

    • Two approximately 128 px account cards appear side-by-side
    • Four destinations occupy a 58 px bottom navigation

Explore Atlas Thread from its first screen.

Open the browser experience, then use its connected navigation to inspect the complete concept route by route.

Launch Atlas Thread