Shipping App Updates: The Installed Version Does Not Move with the Repository
Prompted by the Baro Toilet and WakeProof updates, a look at how app releases differ from web deployments: installed users, existing settings, and the scope of post-release checks.
Joohwan Yu · Founder, Full Stack Developer
Toris · Published
Contents
On September 8, there were records of Google Play update releases for Baro Toilet (바로화장실) and WakeProof. In the course of building and running several apps, release became not the point where the code ends but the point where I rethink the installed product. There were parts that are easy to miss with only the instincts familiar from the web.
The New Version and Existing Users Coexist
When you change server code, the next request can already see the new behavior. With a mobile app, users can keep using an older version. If you judge only by the latest code in the repository, you can miss the combination actually in use. If the app talks to a server, you also have to consider that the old request format may linger.
Conversely, for an app that mostly works inside the device, stored settings and the device environment can matter more than server compatibility. WakeProof is introduced as an alarm app used on the device without an account. For this kind of product, how the user’s existing settings carry over after an update is the key thing to check.
A Successful Release Does Not Replace All Verification
The fact that an update reached the store is an important result. But it does not mean the expected behavior was confirmed on every device. A feature like an alarm, whose moment of use comes later, is hard to verify well by just opening the app once.
I am leaving these as review items for the next release: updating from an existing installation, confirming settings are preserved, and re-running the core feature. Looking only at a freshly installed app misses the link to the earlier state. I also need to note which devices and versions I checked on so I can trace the same problem later.
Write Release Notes from the User’s Viewpoint Too
Rather than listing internal implementation names, it is better to explain what changed and what the user should check. From now on, I will leave a one-sentence user-visible outcome for each change. If it ends at “stability improvements,” I will later have to search again for what problem I was handling.
What I learned from running apps is that the number of releases does not substitute for product quality. Next time, I will include in the work what to check after pressing the release button. Carrying over the state of people who have already installed it was as important as the first screen for new users.
Related project: WakeProof
Advertisement