Skip to content
academia.sh

Unit 03 of 03

Distribution

App package formats optimized per device, the version code and name scheme, automated building and signing, internal, closed and open testing tracks, staged rollout and halting, store review, and post-release monitoring.

Published Updated

Lessons

  1. 01 App Package Formats The app bundle, the APK and the split APK decide which files reach a device. The lesson compares the number of files that land on a configuration with a budget and shows that the universal package overruns it on every configuration. 15 min read
  2. 02 Version Management The version code is the integer the platform compares, while the version name is the string shown to the user. The lesson compares how far the installed version codes of eight devices are from the latest release with a budget and shows that changing the version name does not change the distance. 14 min read
  3. 03 Continuous Integration and Delivery Measures how many jobs the pipeline runs when a change arrives. The change filter runs only the jobs of the affected modules; changes that touch the shared module exceed the budget, and an unfiltered pipeline runs every job on every change. 14 min read
  4. 04 Testing Tracks Measures how many steps a build takes to pass through the internal, closed and open testing tracks and reach production. Shows how the overrun changes when a rejected build is rebuilt and its steps are counted again from the start. 14 min read
  5. 05 Staged Rollout Widens a release to the user base stage by stage and compares the crash count at each stage with an error threshold. Shows that halting at the stage where the overrun appears stops collecting samples for the later stages, and why the sample count needs to be at least four. 14 min read
  6. 06 Store Review and Policies Counts, per module, the permissions the app declares but does not use, and compares the count with a budget. Shows how the overrun closes once the unused permissions are removed, and that the rule does not see the weight of a finding. 14 min read
  7. 07 Post-Release Monitoring Compares each day's crash count in the monitoring window after release with the error threshold. Measures how the jump in the first days leaves the overrun at minority, and how the same counts change category when summed weekly and the sample count drops; then gathers the course's 19 lessons in one table. 10 min read

Start typing to search.

↑↓ ↵ Esc navigate · open · close