Solving a Rubik’s Cube. Skiing uphill. Completing Goldeneye on the N64 and looking suave when standing next to George Clooney. These are all things which are harder than marketing your product to developers. But, to be honest, we can’t think of too many more. We’ve tried everything to promote Bugfender to the development community. Being developers ourselves, we should have known how difficult this would be.
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.
As developers at Mobile Jazz, we know the headache of finding, reproducing, and fixing bugs in mobile apps. Several years ago, we got so fed up debugging mobile apps remotely that we started building a solution for ourselves. We did it by creating a way to remotely access the logging facilities of users’ devices. We built a makeshift server for application logs that allowed us to fix bugs across devices and continents.
Bugfender 2.0 is Live: Over the past year we’ve been hard at work developing Bugfender 2.0, and we’re proud to announce it’s now live. To get started, simply log into your Bugfender account!
We’ve often asked ourselves: What’s the most natural way to provide customer support to our users?
If you have an application that collects personal data with users in Europe, you’ll soon need to comply with a new European directive called the General Data Protection Regulation (GDPR).
We’re here to attest to the strength of the generalist (just in case Shakespeare hadn’t already proven himself). In fact, when we lost our push notification provider, we put two new providers head-to-head—one generalist versus one specialist. The result wasn’t so clear cut.
