Making breaking API changes without breaking your consumer app
At Swiggy, we saw an emerging business opportunity during COVID and made quick work of releasing an app. We went fully native because Flutter made it really, really easy.
3 weeks in, we're pivoting left, right, and center. After releasing version 85, 10% of our users are still on version 1. Now, we didn't build force updates into version 1, and even if we had, we're not sure if demanding an update is acceptable UX for a new app.
So when business demands a new feature that breaks the consumer app APIs, we resort to some non-traditional use of PostgreSQL magic.