The map
- Not started
- In progress
- Done
- Builds on
- 01The processWho starts it, who kills it0/4
- 02The screen and its dataCompose, state, storage, network0/4
- 03Beyond the screenBackground, permissions, push, release0/4
- 04Next: system designSame ideas, at service scale
- Retry with backoff and jitterLibrary ↗WorkManager's backoff policy and every flaky mobile request need the same rule: wait longer each time, and add jitter so a million phones don't retry together.
- Idempotency keysLibrary ↗A worker that is retried, or a push that arrives twice, must not create two orders. Give each operation a key the server can recognise.
- Backend for frontendLibrary ↗Mobile clients pay for every round trip and can't be updated on demand. A backend shaped for the app keeps payloads small and changes on the server.
Written for current Android (API 34 and 35) and Kotlin 2.x. Where behaviour depends on the Android version or on a library version, the topic says so.