Mobile principal in two weeks.
One edit, made in a basement with no signal, followed all the way to a supervisor’s tablet. Then the same parts rebuilt as chat, checkout, a feed and a release platform. Each day is one complete lesson, from the basics up, and picks up where the last one stopped. You can read it with nothing else open.
Week 1: One edit, end to end
Follow Priya's edit from a tap in a basement to her supervisor's tablet, and build each part as you meet it.
- 1BasementA leaking valve, two floors undergroundWhy can't a mobile app treat the server as its source of truth?
- 2SaveOne transaction, two rowsHow do you save an edit so a crash can never lose it or half-send it?
- 3Wake-upNinety-two minutes of nothingWith the app closed, who decides when your code runs?
- 4Sync run2.1 seconds at 4:12 pmWhat exactly happens in one sync run, and how does it recover from a failure at any step?
- 5CollisionLeaking or replaced?When two people change the same thing offline, who wins?
- 6ServerInside the push, and out to Dev's tabletHow does one server stay correct and alive when every phone retries?
- 7Big filesArjun's 412 MB videoHow do you move a huge file over a bad network from an app the user can close?
- 8Mock one · MockCheckpoint: tell the whole story in 45 minutesCan you design the whole system without notes, against a clock?
Week 2: Same parts, new products
Each day changes one constraint. You will notice how much you already know.
- 9ScreenEleven green ticks and one amber badgeHow does a screen stay simple while all of this happens underneath it?
- 10ChatNow the edit is a messageWhat changes when the same design must also feel live?
- 11PaymentsWhen a duplicate costs real moneyWhat changes when you can't let the app decide, and can't get it wrong?
- 12FeedNearly all reads, on a mid-range phoneWhat changes when the hard part is speed, not correctness?
- 13PlatformYou can't roll back a phoneHow do you keep all of this working as 150 engineers keep changing it?
- 14The loop · MockA problem you haven't seenCan you use all of this on something new, and tell the story of why?
See the whole journey
Priya changes valve 3. Step through what happens.Priya taps leaking
No signal, and no waiting. One transaction writes the answer and an outbox row.
Learn this on Day 2 →- valve_3 on her phone
- leaking
- Row shows
- clock (pending)
- Outbox
- op 7f3a, base version 4
- Server's valve_3
- ok, version 4
Six ideas that connect it all
The same parts, in different productsLocal truth
The screen reads a local store. The network only updates that store.
Idempotency key
A key made before the first send turns a retry into a no-op.
Durable queue and retry
Work goes on disk first. A later process runs it, with backoff and jitter.
Cursor and sequence
An ordered number lets any client say: give me everything after this.
The OS decides when
Request work with conditions, and design for it running late or never.
You can't recall a phone
Old versions live for years, so ship in stages and keep a remote off switch.