A small fall
and going from active to passive
Hello friends 👋
The past week was a bit hectic. I'd made a mistake and was busy fixing it. Once all was good, I slowed down and took time to relax.
A Small Fall
As you probably know, last week we released the new Mockup update.
And, even though I took time to test it on different platform versions and devices, a bug has slipped in. A critical bug, crashing the app when accessing the color picker — a widely used feature.
Such kinds of bugs are bad on multiple levels.
It disrupts the workflow of our current users. It gives a horrible impression to newcomers who just discovered the app. It dents our App Store ratings, and increases uninstalls, subscription cancellations, and refund requests.
Overall, it is detrimental and damaging to both the brand and the business.
Once I saw the logs and users' feedback, I located the bug, addressed it, submitted the update, and requested an expedited review from Apple.
From Active to Passive
In the software world, bugs are inevitable. However, what struck me most was the shift from an active, planned approach to a reactive, urgent one.
In my routine, I usually plan and proactively work on new features and address minor bugs. Yet, in such situations, I found myself reacting, shifting from my planned agenda to handling the crisis, while thinking of ways to lessen the damage.
This alone was a great incentive for me to reevaluate and enhance my testing strategies to avoid a similar scenario in the future.
That's it for this week. Thank you for reading.