How to Decide on Mobile Bug Fixes

Any software product being it a web, mobile or desktop application is under suspicion unless it proves that the features are working as expected. In short, software is never bug free. Depending on the software product, fixing bugs in production is not easy and in most cases it’s expensive.

Let’s take a look on how to integrate bug fixes into a native mobile application after the app was released.

Test the App Before the Release

Before a mobile development team is shipping a native app to the app store an intensive testing phase must happen. To minimize the likelihood of doing a hotfix, an extended internal testing phase within the team or company is needed. If the team has the possibility to distribute the app to beta testers or external testing providers to gain early feedback is another approach to take. However, we all know that the real nasty bugs happen in the wild on the customer phones in sometimes weird circumstances.

But how to deal with bugs that have been reported by customers, or the team has found them, after the app was available in the app store?

Is the bug a critical one? Or is it something the team can fix in an upcoming release? Finding the right balance between performing a hotfix or not is not easy.

However, if you want to know how to decide which mobile bugs is worth doing a hotfix and which not, I highly recommend you to read my latest blog post I wrote for Applause here: