Release and Operations

Lessons

1. 01 Mobile Continuous Delivery Mobile continuous delivery turns a code change into a signed build and passes it through a test distribution channel and store review. This lesson measures how well a feature works when the same signed build ships to production with a closed flag. 14 min read
2. 02 Version Management Version management governs which build of an application ships under which number and how the client talks to the server. This lesson measures how well a feature works when it asks for a new contract from a server that offers only the old one. 13 min read
3. 03 Staged Rollout and Rollback A staged rollout opens a new version to only a portion of the users; if a problem appears, the rollout is halted or the feature is turned off. This lesson measures how well a feature works in each bucket the rollout has reached. 13 min read
4. 04 Forced Update Strategy A forced update strategy decides when, with which prompt, and for which reason old clients that the server no longer supports are directed to the new version. This lesson measures how well the payment feature works on a client below the minimum version. 13 min read
5. 05 App Size Management App size management decides what the first download contains and which parts are fetched later on demand. This lesson measures how well a feature that depends on an asset pack not delivered in the first download works. 10 min read
6. 06 Crash and Usage Monitoring Crash and usage monitoring describes how to collect, from both platforms in a unified form, what a released build does in the field. This lesson measures that a crash report created in an offline session stays deferred and that user consent turns usage events off. 13 min read