Mobile Delivery
Mobile teams whose release cadence is set by store review rather than by their own decisions.
Length
5 weeks, part-time
Commitment
~5 hours per week
Cohort
12 live sessions, 20 seats
What this track assumes
A shipping mobile application.
What you cover
5 modules
Each one is worked through live, then built on between sessions.
- 01Store review as a transaction cost, and the release train that absorbs it
- 02Decoupling shipping from revealing — flags, remote config, kill switches
- 03Staged rollout with automated halt criteria tied to release health
- 04Version fragmentation, API compatibility and forced upgrade
- 05Release health instrumentation and acting on it
You build it, then you defend it.
There is no exam and no pass for attendance. Some people do not pass first time.
The project
A release-path analysis and a working staged-rollout configuration for your own application, with halt criteria defined and justified.
Read first
Some of this is free
The knowledge library covers a good deal of the same ground. Start there, and pay us only once you have decided the reviewed version is worth it.
Continuous Delivery Through App Store Review
Store review is the one place a third party sits between your merge and your users. It is a fixed cost in the batch-size equation, not a wall, and the monthly cadence it seems to force is a choice.
Feature Flags And Staged Rollout On Mobile
On mobile you cannot roll back, so flags are not a convenience — they are the safety mechanism that replaces rollback. Remote config architecture, kill switches, default-off discipline, flag debt, and rollout halts that fire without a human.
Mobile Release Health And Observability
What to instrument on a client you cannot attach a debugger to, which signals deserve an automated rollout halt, and how to tell a real regression from noise when early updaters skew every number.
Native Versus Cross Platform Economics
The shared-code decision is an economic one, not a technical preference. What genuinely shares, what never does, the residue that eats the savings, and how to make the decision once so it is not relitigated every quarter.
Other tracks
The rest of the technical family
AI Foundations
6 weeks, part-time
People who already use these tools daily and want to build with them — analysts, product people, and engineers early in their careers.
AI-Native Delivery
5 weeks, part-time
Teams adopting AI-assisted engineering who want the throughput gain to survive contact with review and production.
AI Engineering
8 weeks, part-time
Engineers building LLM applications, retrieval systems and agents who need them to hold up in production.
Agentic Systems Engineering
7 weeks, part-time
Engineers building systems that act on their own, and the leads accountable for what those systems do unsupervised.
Physical AI
7 weeks, part-time
Engineers moving from software-only AI to systems that act in the world, where being confidently wrong has consequences you cannot undo.
Web3 & Smart Contract Security
10 weeks, part-time
Engineers moving into contract development, and teams preparing a protocol for audit and mainnet.
Take Mobile Delivery.
6 weeks, 12 live sessions, 20 seats, priced by region from $450. Places in the first cohorts are arranged directly.