Shipped 8 updates in 2 weeks. Turns out my most active users hated it.
by•
Every time I found a bug, I'd fix it and push a release. Felt super productive.
Then one of my daily users told me, "I keep getting update prompts." Ouch. The people who use it the most were the ones I was bugging the most.
So now I try to bundle fixes and ship every week or two, and only force an update when it really matters. The catch is that known bugs stick around longer.
How do you guys handle this? Ship the fix right away, or wait for the next release?
15 views
Replies
What took the pressure off for me was moving as much as possible out of the app binary, so that a lot of fixes are not app updates at all. The generation logic, prices, the copy of reminders and pushes, which engine handles a request, all of it lives on the backend or in a config document I can edit from an admin panel. A bug there gets fixed the same hour and nobody sees a prompt. The rule that makes it safe is that every backend change has to stay compatible with older app versions still out there, because a share of users never update. So the app release is left for things that really live on the device, and those go out bundled. Your weekly rhythm sounds right for that part. The question I ask about a bug is not how bad it is, but where the fix lives.