Secret Sauce of Cross-platform Mobile App Continuous Delivery
summary
Offshore teams ship cross‑platform apps with monthly date-based releases and a strict Git workflow that keeps everyone merging to master branch only so releases are cut directly from master. Releases run a two‑week internal beta via Google Play testing, then a two‑week freeze before App Store submission; backend is deployed with the binary and a separate web push first to avoid mismatches. Runtime behavior is controlled by server-side JSON feature flags (Eureka service) and CodePush‑style live web component updates plus analytics and a shake‑to‑report screenshot plugin.
AI-written summary · about
chapters (13)
- 0:00Introduction to talk
- 1:02Offshore mobile app challenges
- 9:30Cross-platform team restructuring
- 11:59Simplified branching strategy
- 15:15Monthly release cycles
- 17:23Mobile vs web testing approach
- 20:48Cold push and release process
- 23:45Backward compatibility techniques
- 27:42Stakeholder feedback tools
- 30:34Dynamic configuration with Eureka
- 36:03Feature flag implementation
- 39:14Open-source plugin plans
- 40:41Debug mode and manifest setup
related talks
46mContinuous Delivery for Native Apps
47mMobile DevOps - Deliver great apps continuously
15mWeb-like Release Agility for Native Apps
38mFrom Development to Production: Tips to Optimise Android App Deployments
26mContinuous Everything in Mobile
17mStreamlining Mobile Releases
35mRelease Android apps globally with no headache and minimum stress
30mCI Recipes and Release Flow Strategies for Medium and Larger Apps