We’re really happy to announce that Bugfender 2.0 went live in last quarter – a long awaited release that brings many feature requests from our users. We’d like to take this opportunity to thank you all for your feedback. It’s truly invaluable and helps us to improve Bugfender every day. As some of you may be aware, the service experienced some occasional down time during June.

We created this resource to solve one basic problem: Once you go through all the work of building an app, how can you be sure to nail the landing? In the rush to get an app out, many developers can forget to tag releases or lose depository information that simply needed to be earmarked for a future update. There are some final security measures that need to be taken to protect your app. Whether it’s due to excitement or fatigue, it happens.

In 2016, on the eve of the Black Friday sales frenzy in the US, a research firm called Apteligent released a report estimating how much money firms could lose if their apps crashed on the big day. The report tallied up the amount of money spent by retail app customers on Black Friday the previous year and worked out what would happen if every customer experienced at least one crash during peak hours.

I’d like to offer a heartfelt apology to all of our users who have experienced any downtime and issues with Bugfender recently. We’re really sorry these have occured and for all of the inconveniences they may have caused you. We understand that many people rely on Bugfender to help them in their daily duties and that our service has let you down.