For Expo & React Native
In-appfeedback& release notesforExpoapps
Bug reports with full device context, plus feature requests, straight from inside your app. Publish release notes in the same place. No monitoring suite to run beside it.
acme-mobile
Profile
Tap the button. It is a real flow
Pull-to-refresh flickers on Android
sam@acme.dev · Pixel 8 · 1.2.2 (4182)
Deep link opens the wrong screen
jo@acme.dev · iPhone 13 · 1.2.1 (4090)
The whole loop,
nothing extra
A report arrives with its device context, you triage it, and your users read the release note when you ship.
Collect
01
Bug reports with useful context
Capture bug details, reporter info, app version, device data, and attachments so every report starts with enough detail to act on.
Crash when opening the Profile tab
alex@acme.dev · iPhone 15 Pro · 1.2.2 (4182)
Pull-to-refresh flickers on Android
sam@acme.dev · Pixel 8 · 1.2.2 (4182)
Triage
02
Track it without building a workflow
Update status, set priority, comment internally, and keep a clear record of what changed.
Publish
03
Release notes, next to the product
Write a note for each version so your changelog stays where the work happens and your users know what changed.
v1.2.3
Published- Fixed the Profile tab crash for users without an avatar.
- Faster cold start on Android.
Install
04
Built for Expo and React Native
Create an app, generate an API key, install the SDK, and start receiving reports without wiring together multiple services.
- Setup
- One provider
- Native config
- None
- Types
- Shipped
- Expo Go
- Supported
Setup to first bug report
in minutes
Create your app, connect the SDK, and start collecting reports with the device, OS, and app version already attached.
01Set up
Create your app and generate an API key.
One project per app. Keys are scoped to it, rotatable, and safe to ship in a client build.
02Install
Install the SDK and wrap your root layout.
One provider, one prop. No native config and no custom dev client, so it runs in Expo Go.
03Collect
Reports arrive with the context already attached.
Device, OS, build number, locale, and a screenshot, so you stop asking which version they were on.
04Ship
Publish the release note from the report.
The reporter sees their bug closed, everyone else sees the changelog on next launch.
A better way
to handle bugs
Four habits most small teams inherit by accident, and what replaces them once feedback has a home.
Priced for an app
that isn't earning yet
Start free. Pay when your report volume outgrows the free tier, not before.
What Mite is, and what it isn't
Is Mite a full crash analytics platform?
No. Mite collects in-app feedback and publishes release notes for Expo and React Native apps. It records what a user chose to report, not what the runtime did, so pair it with Sentry or Bugsnag if you need crash capture too.
Who is Mite for?
Indie developers and small teams building mobile apps with Expo or React Native.
How long does setup take?
If your app is already running, you can create an app, generate a key, install the SDK, and send your first report in a few minutes.
Why use Mite instead of a bigger platform?
Bigger platforms bundle crash capture, session replay, and performance monitoring, and they price for teams with a tooling budget. If all you want is feedback and release notes, you pay for the rest anyway. Mite covers that one job at a price a pre-revenue app can carry.