How Swiggy Uses In-App Update API for Better App Adoption
Article Summary
Swiggy got 700,000 users to update their app in one week without sending them to the Play Store. Here's how they did it.
Swiggy's engineering team implemented Google's In-App Update API to solve a common problem: getting users to adopt the latest app version. They chose the flexible update flow, allowing downloads in the background while users continue ordering food.
Key Takeaways
- 16% click-to-impression conversion rate on update prompts
- 700,000 users updated via in-app flow in first week
- Smart config limits prompts and resets post-update
- Flexible flow downloads in background, installs on user confirmation
- Consistent update status shown in accounts section
Swiggy achieved a massive increase in adoption rates by implementing in-app updates with smart frequency controls and persistent UI indicators.
About This Article
Swiggy needed users to update their app for bug fixes, security patches, and new features. The problem was that many users wouldn't go to the Play Store to manually update.
Sarabjeet Singh's team used Google's In-App Update API with AppUpdateManager and InstallStateUpdatedListener. This let users download updates in the background without leaving the app, and they could choose when to install.
Swiggy could now control update prompts through server-side smart config, limiting how often they appeared and resetting them after updates. This reduced friction while keeping users engaged with update notifications.