This is one of the biggest advantages of Bugfender. Crash reporting tools like Crashlytics, Bugfender, 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 log both crashes and non-crashes, you can dive deep into the internals of your application and inspect those problems on your user’s devices without violating their privacy.

Did this answer your question?