Mobile App Analytics for React Native and Flutter — Screens, Crashes, and User Behavior
How to add mobile analytics to React Native and Flutter apps—screen tracking, crash events, iOS vs Android splits, user identification, and connecting app behavior to your website data.
Most products today have a website and an app. Too often, they're measured in completely different tools, so nobody can answer simple questions like "do users who sign up on web activate in the app?" If your app is built with React Native or Flutter, you can track both on one platform.
Table of Contents
- What Mobile Analytics Should Tell You
- Install the SDK
- Track Screens Explicitly
- Identify Users Across Web and App
- Crashes and Errors
- Reports to Check Weekly
- Key Takeaways
What Mobile Analytics Should Tell You
- Which screens users visit and where they drop off
- Crash events and which app versions/platforms are affected
- iOS vs Android differences in engagement
- Funnels for onboarding, purchase, and key actions
- How app behavior connects to web signups and marketing
Install the SDK
DeepSync offers SDKs for both frameworks on Pro and above:
Both use the same session and event model as the web SDK, so funnels and goals work the same way.
Track Screens Explicitly
There's no URL history in a native app for an SDK to hook into, so screen navigation must be reported explicitly. Call trackScreenView from your navigation layer—React Navigation's state change listener in React Native, or a NavigatorObserver / router listener in Flutter.
Name screens consistently
Use stable names like "Onboarding/Step2" rather than dynamic titles. Consistent names make funnels and reports readable.
Identify Users Across Web and App
Call identify after login in both your web app and mobile app with the same user ID. That links a person's web and app sessions so you can see cross-platform journeys—for example, "signed up on web from a Google ad, activated in the iOS app three days later." See the SDK API.
Crashes and Errors
Mobile analytics reports crash events with platform splits. Pair this with screen data: a crash concentrated on one screen on Android after a release is a clear, actionable signal.
Reports to Check Weekly
| Report | Question |
|---|---|
| Top screens | Where do users spend time? |
| Onboarding funnel | Which step loses the most new users? |
| Crashes by platform | Did the latest release break something on one OS? |
| Platform split | Is engagement lower on Android or iOS? |
| Attribution | Which campaigns produce users who activate? |
Key Takeaways
- Track web and app on one platform to see full customer journeys.
- Report screens explicitly with trackScreenView.
- Identify users with the same ID across platforms.
- Watch crashes by platform after every release.
Conclusion
Your users don't think in "web" and "app"—they think in tasks. Measure them the same way.
Frequently Asked Questions
Related articles
Stay in the loop
Get the latest insights on product analytics and user behavior delivered to your inbox.
