Mobile Release Evolution
summary
XING moves from sporadic, months‑long releases to a centralized release train that coordinates ~12–13 domain teams and a dedicated release team, cutting time from several months to about 3 weeks from feature start to user and running nominally two‑week cycles that in practice slip to three. Test automation standardizes on calabash for cross‑platform UI tests, internal iOS prereleases and Android beta rollouts replace ad hoc staging, and phased rollouts avoid overlapping versions.
AI-written summary · about
chapters (4)
related talks
18mManaging Change
32mRunning An Effective Mobile Engineering Team
22mFrom Chaos to Control: Future-Proofing Your Android Release Process
11mWorking with sharp tools - A case study of Continuous deployment
35mTaming a beast
11mStarting Small to Growing Big
01h 02mScaling a mobile project across multiple teams and products
40mHow to build Mobile DevOps for X-plat applications