Keeping my sanity, when white-labeling 40 apps
summary
Reach plc manages 45 white‑label Android apps by extracting long flavor and signing lists into a separate flavors.gradle extraction, generating per‑flavor config.xml and colors from a Google Form, and using a Ruby script to print SHA1/SHA256 certs and daily unit tests to verify digital asset links. CI uses a Jenkins matrix with fastlane to select publications and upload bundles, and screenshots are automated with Espresso-based automated screenshots plus fastlane frameit; staged rollouts and per‑app Firebase/projects reduce risk.
AI-written summary · about
chapters (10)
- 0:00Introduction and context
- 1:58Managing flavors and signing configs
- 5:51Handling certificates and app links
- 8:22Local and remote configuration
- 11:46Creating new apps efficiently
- 13:54CI/CD with Jenkins and Fastlane
- 15:02Automating screenshots
- 16:06Play Store challenges and solutions
- 17:16Managing third-party services
- 18:28Q&A session
related talks
30mJourney of the Android white label process
37mWrite once, ship multiple times
41mWrite once, ship multiple times
34mKeynote: Comedy Talk - Better Android Development (BAD)
23mModularizing Your App
37mScaling App development at Zalando
17mBest Practises for Android Development as a Daily Business
47mClaude Code at Scale: An Android Deep Dive