Tales of a Mobile DevOps
summary
Argument: strong blameless culture drives faster, safer mobile delivery — not new processes. Specifics: adopt release trains and staged rollouts (1, 5, 10%) with remote config so bad releases get killed; use merge queues to avoid simultaneous-PR breakage; measure developer slowness with Gradle Enterprise / profiler and build IDE plugins for faster feedback; detect/linters (Error Prone, Detekt) plus Firebase Crashlytics and Splunk for observability; mitigate flakiness by rerunning tests up to 10 times with an 80% pass threshold.
AI-written summary · about
chapters (7)
- 0:00Start
- 2:07MOBILE DEVOPS
- 4:26PLATFORM TEAM.
- 7:33THE WHO CULTURE
- 8:57DEVELOPMENT.
- 12:52MERGE.
- 22:46RELEASE TRAINS.
