skip to content

Navigation & Entry Points

Navigation as state: a route stack that deep links, notification taps and sign-in gates must rebuild into a valid back stack. Interviewers probe cold starts, fresh installs and signed-out users.

on this pageshow

explore

questions

6

In a mobile app's design, what does it mean to model navigation as state, a stack of routes, and what does it make possible?

level: juniorimportance: should knowfreq 38%

basics

~20 s

Navigation becomes an ordered stack of routes, each a destination name plus small arguments such as a listing ID, start destination at the bottom, visible screen on top. As plain data, it can be built, checked and saved by any entry point.

open as a page

In a second-hand marketplace mobile app, how should a tap on an 'offer received' notification become a screen stack the app can trust?

level: middleimportance: should knowfreq 40%

basics

~20 s

Treat the tap as one more entry point: the payload names a route with offer, listing and recipient-account IDs, the link resolver builds the stack, and the screen loads the offer's current state, not the notification's copy.

open as a page

In a modular second-hand marketplace mobile app, how should the listing feature open checkout without importing the checkout feature's screen?

level: seniorimportance: should knowfreq 28%

basics

~20 s

Through a route contract: checkout publishes a small route type, checkout with a listing ID, in a contract module both features depend on, and the app shell maps routes to screens. Features exchange IDs, never screens or objects.

open as a page