Delivering a Million Downloads Every Week
Article Summary
Swiggy's Android team serves 1M+ downloads weekly with 52% of users updating within 5 days. That velocity could be a disaster without bulletproof automation.
Farhan Rasheed from Swiggy's Android team shares how they compressed release cycles while maintaining stability at scale. The solution? Automating every step from PR creation to Play Store deployment using GitHub APIs, Slack bots, and custom tooling.
Key Takeaways
- Custom Slack bot generates 10+ builds daily for 100+ stakeholders across teams
- GitHub checks run lint, unit tests, and image compression on every PR
- Automated review comments pinpoint exact lines violating coding standards
- Custom lint checks ensure automation testing compatibility across the codebase
- APK comparison tool catches size bloat before production release
By automating their entire release pipeline with GitHub APIs and Slack integrations, Swiggy maintains high stability while shipping features faster to millions of active users.
About This Article
Swiggy's Android team was dealing with release-breaking changes and quality issues even though 52% of users had adopted the new version within 5 days. This put millions of active users at risk of unstable releases and a poor experience.
Farhan Rasheed's team set up GitHub checks API to run lint checks using detekt, checkstyle, and PMD. They added unit tests with jacoco coverage and built custom lint checks to ensure automation testing compatibility. All of this ran automatically on every pull request.
The team kept app stability high while letting developers ship features faster. A custom Slack bot now generates 10+ builds daily for over 100 cross-functional stakeholders without anyone having to manually distribute them.
