Tales of a Mobile DevOps
summary
Argues that mobile DevOps starts with a blameless culture and a platform team that shepherds not gatekeeps, then lays out five concrete phases—code, merge, analyze, test, measure—and the practices that make them work: mono‑repo options (Gradle/Bazel/Buck), CI with merge queues (mergequeue.com), build telemetry (Gradle Enterprise / Gradle Doctor), custom lint rules (Detekt), dependency checking (OWASP dependency‑check), selective UI tests on Firebase Test Lab or Genymotion, release trains + feature flags (Firebase Remote Config), realtime crash/metrics (Crashlytics/Bugsnag) and on‑call+postmortems.
AI-written summary · about
chapters (14)
- 0:00Introduction to mobile DevOps
- 1:49Culture as DevOps foundation
- 4:43Role of platform teams
- 9:59Development phase overview
- 10:22Code ownership and sharing
- 13:31Merge as collaboration
- 17:49Analysis with linters and tests
- 20:38Testing as trust in code
- 23:04Measure user behavior
- 24:05Releasing to production
- 27:16Release cycle management
- 31:11Postmortem process
- 32:16Summary and tools recap
- 33:18Q&A session
related talks
54m[Round Table] MobileOps, an essential approach to mobile development
31mTales of a Mobile DevOps
44mTales of a Mobile DevOps
28mFrom Ooops to Mobile DevOps: 7 Steps for Successful Mobile DevOps Transformation
40mHow to build Mobile DevOps for X-plat applications
48mMobileOps v2, an approach tailored to your organization
23mDevOps Mobile VS DevOps Web
47mMobile DevOps - Deliver great apps continuously
