Shipbook | The remote mobile app logger | iOS & Android

A better way to analyze your mobile app's logs.

Detect issues in your apps

Before your users do. 

sdk open.png
gdpr.png
Patent panding.png
 

Logbook

Behind the scenes look at user activity with full log accessibility to easily find and correct issues

Apps-Log.gif
liglytics.gif

Bridge

Monitor, detect and diagnose through our dashboard to maintain your expected level of excellence

search-app-log-.gif

Loglytics

Proactively catalogue logs according to issue frequency with cutting edge crash reporting

Alerts

Rest assured, the automated alert system will notify you immediately upon detection of issues

New-Alert-.gif

Integrate in minutes!

Get started faster than you can drop anchor

Apple@2x.png

Swift

& Objective-C. 

Android@2x.png

 Java

& Kotlin

+

What is the difference between Firebase Crashlytics and Shipbook?

Crashlytics is a great solution for reporting crashes in your apps. The problem is that it won’t catch all of the other issues that could take place in your app. This is the exact reason we developed Shipbook.
Shipbook remotely stores logs and exceptions from your app’s users in the cloud. This data is crucial to understanding the steps leading up to your app’s crash and helping you discover the solution before your users detect any problem.

Is it possible to use Shipbook and Firebase Crashlytics together?

Absolutely! Shipbook and Crashlytics work together in perfect harmony. Crashlytics alerts you when your app has experienced a crash and Shipbook will help you find out what caused the crash in the first place, displaying the logs that led up to the crash- thereby helping you solve the problem ASAP.

Integrating Shipbook with Crashlytics is a quick and simple solution. Once connected, you’ll be able to open the session of the crash and thanks to Shipbook, you’ll have the full picture and will be able to see all of the actions leading up to the crash.

 

Stop trying to reproduce bugs. Just fix them!

Over the last 30 days, Shipbook has collected and analyzed over

3,540,852,788

logs and exceptions