Working with sharp tools - A case study of Continuous deployment

on YouTube ↗11m

" summary

Beta testers on Android and iOS give reproducible, real‑world bugs that the office cannot, so the team uses a Google+ group, Instabug and email plus weekly cross‑functional meetings to triage, prioritize and ship fixes. A 48‑hour reply target keeps the group alive while developers push experimental UI changes to beta first, then production; concrete wins include fixing position/terminal “stuck” reports and swapping confusing metro line colors after beta feedback.

AI-written summary · about

" chapters (7)

1. 0:00Introduction to beta groups
2. 1:05Initial beta group approach
3. 2:32Improved beta group tools
4. 4:46Beta groups for product development
5. 6:51Testing new OS versions
6. 8:14Maintaining beta group engagement
7. 10:08Closing and key takeaways

" related talks

• 26mContinuous Everything in MobileKeith Ballinger · droidcon Berlin 2016
• 41mShift Left, Shift Right and Improve the CentreAugusto Evangelisti · TestCon Vilnius 2017
• 50mRelease & Iterate Faster: Stop Manual TestingDrew Hannay · Android Summit 2017
• 32mRunning An Effective Mobile Engineering TeamCate Huston · try! Swift India 2017
• 31mDude, Where's My Build? Android CI/CDGautam Korlam · droidCon NYC 2018
• 44mTales of a Mobile DevOpsNicola Corti · Android Summit 2020
• 28mHow to ship apps better, faster, strongerFabien Devos · Android Makers by droidcon 2023
• 10mBeyond “try harder”: Effective strategies to tackle bugsAndy Weir · LDX3 London 2025