← Back to the Yulu case study

yulu — information architecture

Every state the rider app can be in between opening it and finishing a ride, what each one holds, and where it goes when things fail. Built from the same readiness rule the product runs on: required = max(trip × 1.5, 2 km).

5 phases · 12 steps · 12 branch states · 4 cross-cutting layers · 5 persistent surfaces

00Three decisions the whole structure rests on

An IA is mostly the consequences of a few early choices. These are the three that produced everything below — and the third one is the reason this document exists at all.

DECISION 01

Destination is the root of the ride funnel — not the map.

Readiness is trip-dependent, so a bike that clears 3 km does not clear 9 km. That makes the map a result, not a place. If the map were the root, the first screen could only promise a 2 km floor — a weaker guarantee than the product is built to make.

DECISION 02

The funnel is modal, not navigable.

No tab bar once a destination is set. From A7 onward the rider is inside a task holding a payment authorisation and possibly a reserved bike; letting her wander into Account mid-funnel creates states nobody designed. Persistent surfaces hang off A5/A6 only.

DECISION 03

Ride state lives on the server. The app is a view onto it.

The lock's open and close pings define when a ride starts and ends — not the app's buttons. Every entry point is therefore resumable, and a dead phone can't run a fare. This is the single most load-bearing choice in the architecture.

Where decision 03 came from

It wasn't a principle I started with. It came out of one edge case — what happens if the rider's phone dies mid-ride — which exposed an assumption buried in my first model: that the app was the source of truth for when a ride ends. It isn't, and it can't be. If the app owns ride state, a dead battery means a fare running until the bike's does.

Moving authority to the lock pings fixed that, and then paid for itself three more times: it is why F12 needs no on-device screen, why L4 can expire a session mid-ride without interrupting anything, and why going offline at A11 is survivable — the rider locks the bike and walks away, and the receipt catches up when the phone reconnects.

01How to read this

STEP a required node on the spine STATE a variant of a step, not its own destination BRANCH a failure node with a defined return path LAYER a condition that can apply at many steps SURFACE a persistent destination outside the funnel SILENT agent work with no screen at all

The distinction between branch and layer is the one that does the most work here. A branch is somewhere the rider lands; it has a screen and an exit. A layer is a condition — offline, permission denied, session expired — that changes how several steps behave without being a place you can be. Treating connectivity as a branch is how apps end up with a dead-end error screen at every step.

02Launch routing — the question asked before anything renders

Because ride state is server-side, a cold start can't assume it is starting at the beginning. It resolves identity, then an active ride, then an active hold — in that order — and routes past the funnel entirely if either exists. The rider who force-quits mid-ride and reopens the app lands back on her ride, not on a map.

App opens cold or resumed Session valid? token check no E1 → A1 Phone number first run, or signed out yes Active ride? server, not device yes E2 → A10 Live ride skips the funnel entirely no Active hold? 5-minute window yes E3 → A7 Preview countdown still running no E4 → A5 Destination the normal entry ALSO ENTERS HERE — E5 hold-expiring push → A7 · E6 ride ended while the app was dead → A12 receipt · E7 deep link with a destination → A5, prefilled
Launch routing. The order of the two checks is deliberate: ride before hold, because a rider with both is mid-ride and the hold is stale. E6 is the return path for F12 — the rider whose phone died learns the ride ended correctly by being handed the receipt, not by discovering it in a history screen.

03The map — twelve steps and everything that hangs off them

The spine is linear on purpose. The only genuine fork in the whole product is at A5, where a rider without a destination can fall back to a floor-only browse — and that is labelled as the weaker guarantee it is, not offered as an equal path.

Branches sit to the right of the step that produces them. Every one has a stated return path; none is a dead end, and none requires the rider to start over.

SESSION Identity only. No trip exists yet. TRIP Destination known, so readiness is computable. START Money authorised. Bike not yet open. RIDE Live and server-owned. CLOSE Bike returned. Fare settles. A1 Phone number one field A2 Verification 6-digit code A3 First name nothing else asked A4 Wallet skippable — payment moves to A8 A5 Destination the root of the funnel A6 Map + list only bikes that clear this trip A7 Preview + hold range vs. requirement · 5 min A8 Pay at the bike hold, not capture A9 Unlock timer waits for the lock ping A10 Live ride ⇄ Paused fare · range · report an issue A11 Park + lock system confirms, not the rider A12 Receipt adjusted before she asks F1 No bike can make this trip → A5 shorter trip · notify · new area F6 Hold expired — bike taken → A6 F7 Destination changed, bike drops → A6, with the reason stated F8 Payment method declined → A8, another method F2 Lock won't open → retry ×2 → A6 F10 Two riders, same bike → F2 for the second rider F3 Battery dies mid-ride → A11 on foot, fare already stopped F13 Pause cap reached (40 min) → A12, bike released F12 Phone dies / app killed → ends server-side, E6 on return F11 Ended outside a zone → A11, fee stated before committing F5 Lock won't confirm → 'End ride anyway' → A12 F4 Billing evidence ambiguous → review ≤24h, not charged
The ride funnel. Twelve steps, twelve branch states. Note the density: four branches hang off A9–A10, the window between authorising money and the bike being safely returned. That is where the rider is most exposed and where the most design went — and it is also the stretch where the product has least control over the hardware.

04Screen inventory

What each node holds, which agent is working behind it, and where it can go. Silent means the agent is acting with no screen; surfaced means it has become visible because confidence dropped low enough that a human should decide.

IDNodeType What the rider seesWhat the system holds AgentExits
Phase 1 — Session · identity only, no trip exists yet
A1Phone numberStepOne field, numeric keypad open. Errors resolve on blur, never per keystroke.Nothing yet. No account is created until A2 succeeds.absent→ A2
A2VerificationStepSix boxes, one labelled field to assistive tech. Resend reads "Resend in 30s".Session token on success.absent→ A3 · wrong/expired code stays here
A3First nameStepOne field. No surname, email or gender — nothing else is needed to complete a ride.Display name.absent→ A4
A4WalletStepUPI or card, plus "Skip for now". "No deposit, no cash" stated up front.Payment method, or a null that A8 will ask for.absent→ A5 · skip also → A5
Phase 2 — Trip · destination known, so readiness becomes computable
A5DestinationStep (funnel root)Search, recents, saved places. Required range shown per destination before she commits.Trip distance → required = max(trip × 1.5, 2 km).readiness · battery→ A6 · browse fallback → A6 on the 2 km floor
A6Map + listStepOnly bikes that clear this trip. Range in km on each pin, never a battery percentage. The list mirrors the map exactly.Cleared set, and the reason every hidden bike was hidden.readiness→ A7 · zero cleared → F1 · edit → A5
A7Preview + holdStep"24 km on this bike · your trip needs 9.3 km". Marginal notice if it clears by a thin margin. 5-minute hold.Held bike ID, countdown, marginal flag.battery · surfaced when marginal→ A8 · F6 expiry · F7 destination change
Phase 3 — Start · money authorised, bike not yet open
A8Pay at the bikeStepSaved method or entry if skipped at A4. Rates stated. "We place a hold now and charge the actual fare when you finish."Authorisation — a hold, not a capture.absent→ A9 · declined → F8
A9UnlockStepScanner, with manual bike-ID entry at equal weight beside it. "Unlocking…" → "Unlocked. Ride started."Live readiness re-check. The fare timer does not start until the lock confirms open.readiness · live re-check→ A10 · F2 no open ping · F10 taken · F9 wrong bike (silent)
Phase 4 — Ride · live, and owned by the server
A10Live rideStepRunning fare always visible, live range, ETA. One exit: "Report an issue".Telemetry recording — GPS trace, lock events, range curve.battery · billing→ A11 · F3 · F12
A10pPausedState of A10"₹0.50/min · Yulu #4471 held for you." Lower rate, stated before she commits.Pause clock. Auto-prompt at 20 min, auto-end at 40.battery→ A10 resume · F13 at the cap
A10rReport an issueState of A10Four fixed options. She describes nothing.Full telemetry attached automatically — this is the billing agent's evidence, gathered without an interrogation.billing→ A10
Phase 5 — Close · bike returned, fare settles
A11Park + lockStepPosition against the zone boundary. "Confirming the lock…" — the app does not take her word for it.Geofence containment, then the close ping.readiness · verifying close→ A12 · F11 outside zone · F5 no close ping
A12ReceiptStepItemised fare, pause time, adjustment with its reason, skippable rating.Capture against the authorisation. Billing agent's decision recorded with its evidence.billing · surfaced when adjusted→ A5 · ambiguous → F4

05Ride state machine — and who is allowed to change it

The screen inventory describes what the rider is looking at. This describes what is true, which is a different thing and the one that money depends on. Two transitions in here cannot be made by the app at all: the bike has to agree.

PRIMARY PATH none no obligation reserved 5 min, no money authorised hold placed riding fare accrues closing awaiting close ping settled captured A7 A8 lock-open ping A11 lock-close ping paused ₹0.50/min auto-ends at 40 min → F13 → settled TERMINAL EXCEPTIONS voided hold released, ₹0 F2 / F10 — no open ping review not charged meanwhile F4 — evidence ambiguous THE APP CANNOT MAKE — authorised → riding, or closing → settled. Both need the bike. Every button that looks like it does one of these is really a request. Fare accrues in riding and paused only — and stops the instant a failure event fires, not when the ride is formally closed.
Ride state machine. "I've locked it" is a request, not a transition — the state changes when the bike says so. That single rule is what makes F5 survivable: if the close ping never arrives, the rider can still end the ride, the fare stops immediately, and the bike is flagged for pickup rather than the rider being held hostage to hardware.

06Edge cases

Twelve branch states. Read the last two columns together: every one of them resolves in the rider's favour by default, which isn't generosity — it's the behavioural rule from the product spec ("prefer a false negative over a false positive; never resolve ambiguity in the company's favour") expressed as structure rather than asserted in a document.

IDTriggerDetected by What the rider getsReturn path State effectCost to the rider
F1Destination set; nothing in range clears itReadiness, by absenceAn empty map that names the check out loud — "There are bikes here, but none have the range for 6.2 km."Notify me · try a shorter trip · search another areanoneNone. This is the product working.
F2QR scans but no lock-open ping within the timeoutReadiness, live re-check"We haven't started your ride, and your payment hold has been released." Bike drops off the map for everyone.Retry ×2, then A6authorised → voided₹0, stated explicitly — the fear here is being billed for a bike she can't use.
F3Range exhausted before arrival — the prediction was wrongBattery Decay, missedNearest zone distance and walking directions. Adjustment pre-applied and announced here, not deferred to the receipt.→ A11 on footriding → closing, pre-flaggedA walk. Fare stopped at battery death, not at ride end.
F4Gap in telemetry across the disputed windowBilling Resolution → escalate"There's a gap in the ride data around 2:14 pm, so we're checking it manually. You haven't been charged for the disputed time while we look."Human review ≤24h; lands in G3settled → review₹0 pending. The company absorbs the ambiguity, not her.
F5No lock-close ping within ~10s at ride endReadinessPush the lock and retry — then "End ride anyway", which stops the fare immediately and flags the bike for pickup.→ A12closing → settled, flagged₹0 extra. This is Ananya's original bad ride, redesigned.
F65-minute hold elapses before she reaches the bikeHold timerToast on return to the map: "Your hold expired. The bike is available again."→ A6reserved → noneA wasted walk — the reason hold rate is a tracked metric.
F7Destination edited while a hold is active; the held bike no longer clearsReadiness, recomputedThe sheet explains the removal rather than letting it read as a bug: "2 bikes dropped off — they can't make the longer trip."→ A6reserved → noneOne re-pick.
F8Authorisation declined at the bikePayment service"That didn't go through. Try another method." Never blames a specific bank — we don't know.→ A8none — nothing held₹0. Previously entered values persist; no re-typing.
F9She scans a different bike than the one she heldClient-side ID compareNothing. The scan is accepted and the old hold released silently.→ A10hold transfersNone — designed to be a non-event. Don't punish a decision that costs nothing.
F10Two riders scan the same bike within secondsLock state — first confirmed unlock winsThe second rider gets F2: hold released, bike gone from the map.→ F2 → A6authorised → voidedSeconds. Reuses an existing failure state rather than inventing one.
F11End attempted outside every valid zonePolygon containment (deterministic — never a model)End blocked, direction to the nearest zone, and any out-of-zone fee stated before she commits.→ A11stays ridingA walk, or a fee she agreed to in advance — never discovered afterwards.
F12Phone dies, or the app is force-quit mid-rideServer — device heartbeat lostNothing on the device, because there is no device. She locks the bike and walks; the close ping ends the ride. E6 hands her the receipt when she's back.→ E6 → A12riding → settled, server-side₹0 extra. Fare stops at last confirmed movement, not at app reconnection.
F13Pause exceeds the 40-minute capPause timerPrompt at 20 minutes, auto-end at 40, with a push explaining it. A held bike is a bike removed from supply.→ A12paused → settledRide ended for her. A supply decision, communicated — not a punishment.
The pattern worth noticing across the table

Six of the twelve branches cost the rider nothing at all, and the remaining six cost her a walk or a re-pick. None of them cost her money she didn't agree to. That is not twelve separate acts of generosity — it falls out of two structural choices made once: the fare only accrues in riding and paused, and it stops on the failure event rather than when the ride formally closes.

Get those two right and the kind interface writes itself. Get them wrong and no amount of apologetic microcopy saves it.

07Cross-cutting layers

Conditions, not places. Each one changes how several steps behave without ever becoming a screen the rider is stuck on — which is the trap: treat connectivity as a branch and you end up with a dead-end error page at every step of the funnel.

L1Location permission

Denied is a degraded state, not a blocked one — and barely degraded at that.

A5
Unaffected. A destination is typed, not sensed.
A6
Falls back to manual area search. Readiness still works — it needs the destination and the bikes' positions, not hers.
A7
Walk time and distance degrade to approximate. Range framing is untouched.
A11
Zone confirmation uses the bike's GPS, so ending a ride is unaffected.

L2Camera permission

Barely a layer at all, because the alternative was never a fallback.

A9
Manual bike-ID entry sits beside the scanner at equal weight, permission or not. QR scanning needs visual targeting and steady motor control not every rider has.
Everywhere
No blocked screen exists anywhere in the product for a denied camera.

L3Connectivity

The phase you lose signal in decides what happens — and the back half is survivable because the bike holds the truth.

A1–A4
Blocked with retry. Nothing to cache; no account exists yet.
A5–A6
Last-known map with an honest banner, and reservation disabled — readiness can't be verified, so the product won't pretend.
A8–A9
Can't authorise or confirm a lock → F2 path. Nothing charged.
A10
Ride continues; the bike holds lock state. "Reconnecting…", fare accrues server-side, reconciled on return.
A11
Lock it and walk away. The close ping ends the ride; the receipt catches up.
A12
Queued. Appears in G3 when the phone reconnects.

L4Session expiry

Re-auth returns her to the node she was on — never dumped to home, and never mid-ride.

A1–A9
Re-auth, then resume at the same step with form state intact.
A10
The ride is untouched. It lives on the server; expiry is a viewing problem, not a riding problem. Re-auth lands on E2 → A10.
A11–A12
Lock-close still ends the ride. The receipt waits in G3.

08Persistent surfaces

Everything outside the ride funnel. All five hang off A5/A6 only — never reachable from A7 onward, which is Decision 02 enforced structurally rather than by hiding a tab bar. The single exception is the ride screen's "Report an issue", and that returns to the ride rather than leaving it.

IDSurfaceReachable fromWhat it holds, and why it exists here
G1AccountA5 · A6Phone, first name, delete account. Deliberately thin — nothing was collected that would need managing.
G2Payment methodsA5 · A6Add, replace, remove. Separate from A8 because A8 is a step in a task and this is maintenance; collapsing them is how riders end up editing cards while a hold is live.
G3Ride history + receiptsA5 · A6 · pushEvery past ride, including anything in review from F4 and anything settled while the phone was dead from F12. This is the landing place for every asynchronous outcome in the system — without it, F4 and F12 have nowhere to resolve.
G4Saved placesA5Home and Work. Text labels, never icon-only. Feeds the destination-first root so the commute case is two taps.
G5HelpA5 · A6 · G3Report a past ride, contact. Notably not reachable mid-ride: during a ride the relevant control is "Report an issue", which attaches telemetry automatically instead of asking her to explain.

09What this architecture deliberately doesn't have

An IA is defined as much by its omissions, and each of these was a live option that got rejected for a reason.

The one I'd still argue about

Hiding bikes is a strong move with an obvious failure mode: an empty map can read as a broken app rather than a system exercising care. Absence is paid for in two places — F1 naming the check out loud, and A6 narrating removals when the destination changes — but whether that reads as diligence to a first-time rider is untested, and she is exactly the person with no prior trust to draw on.

Hide rate and F1 frequency are the two numbers that would settle it. They're instrumented for that reason, and they're the dial that would move the 1.5× multiplier if it turned out I'd set it too conservatively.