FAQ

Q: What is Bugfender?

Bugfender is a modern remote logger, tailor-made for mobile development. Sounds cheesy, right? Well, here’s what it actually does:

If you’ve ever been involved in the development process of a mobile application, I’m sure you have come across a scenario where you or your developers weren’t able to reproduce a serious bug that some of your customers were experiencing.

To resolve such issues, you’d normally need to connect the problematic device to your development machine via USB. But how could you possibly solve this issue if the customer experiencing it lives 500km away?

Bugfender solves this issue by providing live access to the remote device’s debug log console.

Q: How does that compare to Crashlytics, Bugsense and similar crash reporting tools?

Crash reporting tools like Crashlytics, Bugsense, HockeyApp, Crittercism do exactly what they’re made for. They will report any kind of crash that happens by sending you the stack trace.

However, what if the crash was caused by corrupted data or unexpected behavior? This would never show up in the stack trace. The only way to debug this kind of issue would be to connect the device to your development machine and go through the logs. Bugfender does exactly this, but without the need of having the device right next to you. You can debug the error while your customer is happily playing a game, browsing the web or even while using your application.

Q: What if there’s a problem that doesn’t cause a crash?

This is one of the biggest advantages of Bugfender. Crash reporting tools like Crashlytics, Bugsense, HockeyApp, Crittercism are very limited as they can only react to an actual crash.

What if the user has a problem that doesn’t cause a crash? For example; if the user is trying to log in and the app is stuck showing a loading dialog or if the user is located in Spain and your app constantly recommends restaurants in New York. Those examples are not crashes, but significant issues in the user experience that need to be fixed.

With Bugfender, you can dive deep into the internals of your application and inspect those problems on your user’s devices without violating their privacy.

Q: How do I know if Bugfender is good enough?

Bugfender was born from our own needs, built by developers, for developers.

At Mobile Jazz we’ve been developing mobile applications since 2008, and we’ve built a lot of them. From small startup apps to big name enterprise applications. Many of them have over 10M users, and one over 100M. We really care about high quality, great user experience. On average, our apps have an app store rating of 4.5 stars.

With so many new devices entering the markets every year, it’s getting tougher and tougher to deliver an app with an excellent UX, especially when keeping backward compatibility in mind. Android alone has close to 19,000 devices, which in order to test, would require a lot of devices and a lot of people. It’s virtually impossible to cover all of them.

This is where Bugfender comes in handy. With Bugfender you can access the logs remotely, theoretically on any device, but most importantly on those that are experiencing issues with your app.

Q: I don’t believe you. Can I check it out myself?

Absolutely. Simply sign-up for free and integrate Bugfender into your application. We promise you, it’ll make your life a lot easier within minutes.

Q: I write bug-free code and test extensively. Why would I need Bugfender?

Even though you write bug-free code and test everything on your device, there are certain things you cannot test. One of them is the sheer number of mobile devices out there with all kinds of different screen sizes and various operating systems. Some of them over 5 years old.

So while you think every device works perfectly, in the real world it simply won’t. And there’s no way you can prepare for this, so the best thing you can do is to fix issues as soon as they occur. Having access to the development logs of the affected devices and inspecting what actually causes the problem will save you days if not weeks of speculation, trial, and error.

Q: Does Bugfender only work with mobile devices?

We currently support iOS and Android. Other platforms will follow including web, Windows and macOS. For now, you can send logs from those through our API.

Q: Does Bugfender have any side-effects on the app’s performance and data usage?

UI Performance
Bugfender shouldn’t have an impact on an app’s UI performance as everything is being dispatched to separate threads and fully executed in the background. As long as you don’t perform too much heavy data processing to prepare the log, the interference with the user experience will remain close to zero.

Battery and Data Usage
If the logs are disabled it will almost be negligible.
With logging enabled, battery and data usage will depend on how much data is being logged and how much processing power is needed to acquire and pre-process that data.

Q: What happens to my app if I discontinue my Bugfender subscription?

Bugfender is only active if you ask it to be. If you discontinue a paid Bugfender subscription service, the free Bugfender SDK will stop sending logs to our servers, but will continue to output log files locally on the device just as if you’d used the native logging facilities of your platform.

There’s no problem in leaving the free Bugfender SDK in your application and continuing to use it for your local log output. It’s also convenient in case you’re experiencing problems and want to sign up for the paid Bugfender subscription service again at a later time.

Q: Remote device access. Are you guys the NSA?

We take your privacy very seriously.

Bugfender does not and will never have direct access to your user’s devices. Only the data you decide to send to Bugfender will ever be transferred. It’s always protected by enterprise-grade encryption with Transport Layer Security (TLS), used in electronic banking and health institutions. Moreover, we remove data every 30 days.

Q: Do you use an analytics tool?

As previously stated, your privacy is very important to us and we like to be upfront about the tools we use. We currently use Google Analytics and Mixpanel to learn about how you use our tool. This helps us to improve your experience and create better functionality for Bugfender. We will never forward the log data you send to us.

Mobile Analytics

 

Q: Where can I find your Terms of service?

You can find our Terms of Service here.