Less back-and-forth.
More fixing.

“Something’s broken” is only half the story.
Crumb captures the context, so your team can get to the fix.

Get started with Crumb See how it works

Native mobile reporting. Open-source SDK. Privacy built in.

In their own words.The starting point for a fix.

“Paid for my order and the button just kept spinning.”

SAMPLE BUG REPORT
The details, already there.One snapshot. At report time.
✓
Device
Model & operating system
App
Version & screen
Diagnostics
Captured at report time

Crumb native report form. Review a sample checkout report before sending.

Private before it leaves.

Sensitive inputs masked on-device.

✓
A trail worth following.LOGS
01 App-provided logs
02 A bounded snapshot
03 Sanitized on-device

The breadcrumbs around the problem.

ONE REPORT. THE WHOLE MOMENT. Native iOS · example app

Feels at home in your stack.

iOS Android React Native Expo

FROM “IT BROKE” TO “I SEE IT”

A small report.
A much bigger picture.

Their words. The screen. The state of the app.
Everything captured around one reported moment.

THE CRUMB WORKSPACE

Crumb report detail — loading the interactive sample.
Their words, with the context to investigate.Sample report · captured context

Explore the current Crumb interface. All reports shown are sample data.

01

They spot it.

A shake or a tap opens a native report form, right where the problem happened.

02

Crumb captures it.

A one-time snapshot gathers the screen, app state, and diagnostics. They review what’s shared.

03

You get the context.

Their report and its evidence arrive together. Start investigating with the missing pieces in place.

THOUGHTFUL BY DEFAULT

Good context.
Clear boundaries.

Your users shouldn’t have to trade their privacy for a better bug report.

  • Sensitive stays sensitive.

    Text inputs are masked on-device. Reporters can preview and remove the screenshot before sending.

  • Only when someone asks.

    No session recording or continuous diagnostics. Crumb captures one moment after an explicit report action.

  • Bad connection? Report saved.

    Submitted reports stay in a durable local queue and retry when connectivity returns, even after a restart.

Read the privacy principles
YOUR DEVICE. YOUR DECISION.

Crumb native review screen, with masked screenshot and captured context.

REVIEW WHAT’S ATTACHED. SHARE ON YOUR TERMS.

BUILT FOR YOUR NEXT BUILD

Your next bug report
could tell you more.

Create your workspace, then add Crumb to your app. Give your team a better place to start.

Get started with Crumb
Apache-2.0 SDKPublic preview · 0.0.1-rc.3
COCOAPODS
pod "CrumbSDK", "0.0.1-rc.3"

Also available with Swift Package Manager. Requires iOS 15 or later.

Get the iOS setup guide
1 Install the SDK 2 Configure 3 Send a report

A FEW MORE DETAILS

Frequently asked questions.

Small SDK. No mysteries.

Does Crumb record user sessions?

No. Crumb gathers a bounded, one-time diagnostic snapshot when someone explicitly opens the reporter. It does not record sessions, track navigation, or continuously monitor performance.

Does it work with React Native and Expo?

Yes. The React Native adapter uses Crumb’s native iOS and Android SDKs. Expo requires a development build; Expo Go is not supported because Crumb includes native code.

What happens when a user is offline?

Once the user submits, Crumb saves the sanitized report to an app-private local queue before attempting upload. Submitted reports survive app restarts and retry when connectivity is available.

Can I control what’s captured?

Yes. Configure invocation methods, screenshot capture, custom masking, and bounded log sources in your app. Reporters can preview and remove screenshots before submission. Available diagnostics vary by platform.

Is Crumb open source?

The native SDKs, examples, and public report contracts are open source under Apache-2.0. The hosted Crumb API and dashboard are a separate product. Explore the repository ↗