Didban Mobile Observability

Crash reporting for the mobile app you actually ship.

See what crashed, read the stack trace, and understand the release and actions around every Android or iOS failure.

Get Started Read the Docs
Android iOS● Illustrative product UI
A clearer way to investigate

One issue. The evidence around it.

Didban groups repeated failures, highlights the frame worth opening, and keeps the surrounding release and device context close.

DidbanIllustrative product UIA
Issues / IllegalStateException
New issue

IllegalStateException: Order payload validation failed

com.example.checkout.CheckoutViewModel

Stack trace Retraced
a.b.c.e(:18)
Likely investigation pointCheckoutViewModel.submitOrder()CheckoutViewModel.kt:184
Fragment.performViewCreated
Looper.loopOnce
PLATFORMAndroid
ReleasesRelease 2.4.1
DEVICEPixel 8 · Android 15
FIRST SEENToday, 10:42
Core Capabilities

What you get after a crash

The useful answers first—not a tour of crash-handler internals.

01

Crash reporting

Group Android and iOS failures into issues with the event details that matter.

#8a9f20Grouped
02

Readable stack traces

Retrace R8 / ProGuard, resolve Android native symbols, and symbolicate iOS dSYMs.

a.b.c.e(:18)→CheckoutViewModel.kt:184
03

Breadcrumbs & context

Keep developer-provided milestones close to the crash they explain.

Pre-crash timeline
04

Release tracking

Understand which builds are affected and when an issue regresses.

v2.4.10 regressions
05

App Health

Use foreground session telemetry to understand crash-free and healthy sessions alongside release adoption.

99.2% Healthy
06

ANR detection

Make Android main-thread stalls visible next to fatal crashes.

Main Thread> 5,000ms
Readable stack traces

From opaque frames to source you can act on.

Upload the matching artifacts and investigate retraced Android code, native frames, and iOS crashes with their source context.

Android · R8 / ProGuardAndroid · Native symbolsiOS · dSYM
BEFOREa.b.c.e(:18)0x00000001019a0c
↓Didban
AFTERCheckoutViewModel.submitOrder()CheckoutViewModel.kt:184
BreadcrumbsIllustrative product UI
checkoutCheckout opened
paymentPayment method selected
paymentUser tapped Pay
CRASH
Breadcrumbs & context

Add developer-provided breadcrumbs for the key moments before a failure. Didban keeps the timeline beside the event.

Breadcrumbs are explicitly added by your app. Keep secrets and personal data out of them.

App Health

See sessions and releases in the same investigation flow.

Understand crash-free and healthy sessions, affected releases, and installation activity from actual session telemetry.

App HealthIllustrative product UILast 30 days
Crash-Free Sessions99.2%based on sessions
Healthy Sessions98.7%no crash or ANR
Known Installations4,280active in range
Release 2.4.178%
2.4.018%
2.3.94%
Built for both mobile runtimes

Android and iOS, in one investigation workspace.

Android

JVM crashes, native crashes, ANR detection, R8 / ProGuard retracing, native symbols, releases, sessions, and App Health.

Android docs

iOS

Swift and native fatal crashes, Objective-C exceptions, POSIX signals, dSYM symbolication, releases, sessions, and App Health.

iOS docs
The short version

Capture. Recover. Group. Symbolicate. Investigate.

Didban records a failure, recovers it on a later launch, and turns it into an issue you can investigate. The safety model belongs in the docs.

01Capture→
02Recover→
03Group→
04Symbolicate→
05Investigate
Learn how Didban works
Start with a small integration

Initialize early. Keep moving.

Use the SDK initialization that matches your app, then follow the platform docs for setup details.

Android docs iOS docs 
Didban.init(
    context = this,
    apiKey = "didban_ing_…",
    baseUrl = "https://YOUR_DIDBAN_API"
)

Make the next mobile crash easier to understand.

Start with the documentation or open Didban to create your project.