Skip to content
All books
Stage 5 · System design

Mobile System Design blueprint

Twenty architecture decisions every mobile system meets, each built around one worked failure case, with a rubric to review them.

5.0 · 1 review on Gumroad

About the book

Mobile system design is not a collection of diagrams. It is the work of making decisions while requirements, traffic, teams and platform constraints keep moving.

This book puts you inside realistic iOS and Android scenarios and asks you to frame the problem, choose the tradeoffs, migrate safely, operate the result and preserve a way back.

Each chapter is a working laboratory with a decision record, exercises, field guidance and an answer key, so you practice judgment instead of memorizing architecture vocabulary.

What you get

  • 20 decision chapters, each around one worked failure case
  • 12 longitudinal scenarios, from payments to an AI assistant, each across five stages with an incident
  • 50 scored decision exercises with a complete answer key
  • The Blueprint rubric (7 dimensions, 0 to 28) and five more named frameworks
  • Complete and Master add dark editions, templates, a Swift and Kotlin companion (7 modules) and a toolkit

A page from the book

Copied as printed, so you can judge the format before you buy.

The Blueprint frameworks, page 473

Worked mini-example: scoring a design with the rubric

A team proposes moving conflict resolution for offline notes from last-write-wins to a conflict-free replicated data type. Problem and invariants: 3 (invariant “no user edit is silently lost” is stated). State and authority: 4 (server is the merge authority, clients propose operations, written clearly). Compatibility and evolution: 1 (nothing said about notes created by old clients that still send last-write-wins). Reliability and operations: 2 (rollback exists but no metric detects silent data loss). Security and privacy: 3. Organization and adoption: 3. Evidence and learning: 2. Total 18 of 28. The low compatibility score is the headline: the design is sound in steady state but has no story for the migration window, which is exactly where notes will be lost. The review now has a target.

Want more pages?

What is inside

  1. 011 The architecture decision loopp. 9
  2. 022 Requirements as invariants, budgets, and failure policyp. 23
  3. 033 Client-server boundaries and authorityp. 37
  4. 044 State ownership and canonical sources of truthp. 50
  5. 055 Offline-first beyond cachingp. 63
  6. 066 Synchronization, consistency, and conflict policyp. 76
  7. 077 Idempotency, retries, and persistent state machinesp. 89
  8. 088 Version skew and backward compatibilityp. 102
  9. 099 Schema and data migrationsp. 116
  10. 1010 Background work and process restorationp. 129
  11. 1111 Performance, battery, memory, and thermal budgetsp. 144
  12. 1212 Security, identity, attestation, and privacy boundariesp. 157
  13. 1313 Mobile observability and reliability metricsp. 172
  14. 1414 Release trains, progressive rollout, flags, and kill switchesp. 186
  15. 1515 Incident response when the client cannot be patched immediatelyp. 199
  16. 1616 Modularization, build systems, and CI economicsp. 213
  17. 1717 Shared foundations, SDK design, and developer experiencep. 228
  18. 1818 Platform teams, governance, RFCs, and architecture fitnessp. 241
  19. 1919 Cross-platform ownership boundaries and migration economicsp. 255
  20. 2020 On-device and hybrid AI as a versioned systemp. 268

Who this is for

This is for you ifYou need a repeatable way to make and defend mobile architecture decisions.

  • Senior Engineer
  • Staff candidate
  • Aspiring Mobile Architect
  • Tech Lead
The library pathWhere this fits
  1. 01Get foundThe Silent Rejection
  2. 02Build the record and negotiateThe iOS Engineer playbook · Leverage
  3. 03InterviewThe iOS interview blueprint · The senior signal · Top 300 React Native interview questions · 500 Flutter interview questions · The senior SDET interview handbook
  4. 04Answer practice and live roundsThe 24-hour iOS interview answer book · The 24-hour Android interview answer book · Share your screen
  5. 05Architecture and qualitySwiftUI under load · Mobile System Design blueprint · Security is a feature · The second passYou are here
  6. 06Staff systems and ownershipAltitude · Ticket taker, outcome owner
  7. 07Build with AIBuild with your brain on (coming soon)
  8. 08LeadLeadership blueprint (coming soon)
  9. 09ArchitectArchitect blueprint (coming soon)
Portrait of Mike Salari

About the author

Mike Salari

Staff Mobile Engineer · Mobile Architect · Technical Author

I wrote this from mobile architecture work in fintech and regulated domains where correctness, security and maintainability are not optional.

15 years building production mobile software, with experience across Apple, Adobe, Cisco, Mastercard and Visa. 500+ technical interviews from the hiring side.

Read the full story

Before or after you buy

Not ready yet? Use the system design prompt pack →

Already own it? After the blueprint, move from one design answer to the cross-team scope that makes the decision durable. Add staff-level scope →

Free guides: Mobile system design interview preparation · Offline-first mobile architecture · Mobile data synchronization design

Practice the decisions before production makes them urgent.

Use the method, scenarios and exercises to build mobile architecture judgment you can defend and operate.

Get the book, From $199

Share this book

XLinkedInBlueskyThreadsHacker News