Quality Assurance and Testing for Mobile Applications
Article Summary
Julio Zynger from SoundCloud reveals how they ship mobile releases every two weeks without breaking things. Their secret? A release train model that turns chaos into predictability.
SoundCloud's mobile team publishes new Android apps bi-weekly to millions of users across countless devices. This post breaks down their entire quality assurance process, from automated PR checks to staged rollouts, showing how they balance speed with stability at scale.
Key Takeaways
- Release train model: code freeze every 2 weeks with rotating release captains
- Automated pipeline runs static analysis plus unit, integration, and UI tests on every PR
- Feature flags decouple app releases from feature launches and enable internal testing
- Staged rollouts start with beta channel before gradually reaching production users
- Blameless post-mortems document incidents to prevent future reoccurrence
SoundCloud maintains release quality through predictable two-week trains, extensive automation, and a culture where process improvements matter as much as tooling.
About This Article
SoundCloud pushes Android app updates every two weeks to many different devices and regions. This makes it hard to predict how the app will actually work for users with different setups and needs.
SoundCloud built remote feature toggles that stop problems from spreading when they happen. They also use alpha and beta builds for early testing. This lets them release app updates without waiting for features to be ready.
SoundCloud uses continuous integration with scheduled and event-triggered jobs to keep the master branch ready to deploy at any time. They automate code obfuscation with ProGuard or R8 and automatically update translations for all supported languages.