How should the identity adapt to native iPhone behaviour and different appearances without changing the meaning of the journey?
The integrated layout is a static visual candidate. A native iOS version must reflow around safe areas, Dynamic Type, accessibility focus and system appearance. Apple’s Dark Mode guidance recommends adapting to the person’s appearance setting; Apple accessibility guidance frames legibility and assistive technology as part of the interface, not an optional polish pass.
The current light study puts dark text on warm off-white, lilac in the route shape, and lime in the companion/action. The dark study uses a charcoal field and a warm off-white gate ticket, retaining lilac and lime in the same roles. This is an arrangement Maia described as promising, not a locked palette. The gate code, “previous” label, source status and actions must keep the same reading order in either appearance. A dark mode should not depend on colour inversion alone; surfaces and text need separately checked pairings.
The component-state study exposes an important issue: a layout that looks clear in an idle artboard needs pressed, disabled, loading, stale and unavailable states. The status should be labelled with words. “No update available” and “last updated at…” are different from a confirmed live gate. A design must also avoid using a bright accent as the only sign that a button is selected.
Use native navigation and controls where they help familiarity; keep the branded illustrations decorative. Let text wrap and stack vertically; never compress A04 to make a fixed ticket shape fit. VoiceOver should announce new gate before old gate, and decorative mascot art should be hidden from its reading order. Permission requests for notifications or Bluetooth belong at the point where the traveller chooses the feature. A person who declines either still needs a functional journey.
Compare the alert on a real phone in light, dark, large text and increased-contrast settings. Check contrast of every text/surface combination against WCAG’s minimum contrast guidance as a measurable baseline; inspect colour independently via Use of Colour. Then conduct the same first-glance and dismissal tasks with people. A calculated ratio alone will not show whether the screen feels too busy.
Taking forward — provisional: one identity with system-following light and dark appearances, consistent roles for lilac and lime, and native accessibility behaviour. This page does not lock exact tokens or prove either appearance works for the audience.