Skip to content
Ritesh FirodiyaGet in touch

Work / AskCal / Wiki / Surfaces

splash

Surfacecanonicalverified 2026-09-23

SURFACE.MOBILE.SPLASH

Summary

The deep-green hand-off between launch and the first screen.

Raw wireframe

  • .context/designs/mobile/states/splash.html

Why it is drawn this way

It is drawn because flow.start has to be a real file. The chart ranks every column from the start node, so a set with no declared start ranks every screen at zero and draws one column. This set used to nominate onboarding/welcome as the start, which is what §13 allows only for a product that HAS no splash — and this one does: expo-splash-screen in apps/mobile/app.json. The manifest therefore did not begin where the app begins, and the first back was dead in the wrong place.

#0a3a27, not white. The deep brand green, so the hand-off to Welcome never flashes a colour the app does not otherwise use. resizeMode: contain with splash-icon.png; the asset is shared with the surfaces under designs/brand/ rather than pasted, so it cannot drift from the one the build ships.

Two ways out, and both are real links. A first run goes to Welcome; a returning account is already past it, and that second path is the side edge in routes.js. It is drawn as a quiet line rather than a button because the app makes that choice without asking — the wireframe needs it only so the set can be walked both ways.

Related

Sources

  • .context/designs/mobile/states/splash.html
  • apps/mobile/app.json — expo-splash-screen

Every project of mine is written down like this.

Read the résumé