Hotfix Heaven: Why In-App Updates Are a MUST
summary
Shows concrete setup: uses the Google Play Core in‑app updates library with Flexible vs Immediate flows, sets priority 0–5 and staleness/backoff days, and triggers updates either via the Google Play Publishing API or Firebase Remote Config. Gives three real rescues (bad data migration crash, unversioned backend causing older apps to crash, certificate pinning revocation) where forced immediate updates fixed production issues. Tests with a FakeAppUpdateManager for integration checks, warns about asset pack deletion, Play cache quirks, and that roughly 10–35% of users lag on updates.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:08In-app updates matter
- 3:34Flexible vs immediate flows
- 5:03Why in-app updates are essential
- 6:27Critical update stories
- 8:56Implementing in-app updates
- 13:07Google Play API triggers
- 14:30Firebase Remote Config
- 15:56Testing strategies
- 18:05Internal app sharing
- 19:51FakeAppUpdateManager testing
- 23:01Troubleshooting issues
- 25:07Update adoption stats
- 27:10Update frequency
- 30:57Effective update strategies
- 33:47Summary
- 34:51Q&A
related talks
22mRethinking App Maintenance Screens and Forced Updates
35mFrom fear to air: embracing over-the-air app updates
21mDelivering instant update patches for React Native to 50+ million people
25mLive App Updates Without The App Store
41mRelease management: Successful launches and updates on Google Play
38mFrom Development to Production: Tips to Optimise Android App Deployments
35mRelease Android apps globally with no headache and minimum stress
45mSoftware Updates for Connected Devices: Key Considerations