Datadog · Mobile RUM
Mobile app monitoring for iOS and Android apps, with Datadog RUM
Mobile app monitoring tells you what your customers meet on their own phones: which screens are slow, which actions fail, which release started crashing and which API call kept them waiting. Datadog Real User Monitoring (RUM) does this for native iOS and Android apps and for Flutter and React Native, and links each slow screen to the backend trace behind it. Interkey, an official Datadog partner in Saudi Arabia, sells the Datadog licences, instruments your apps with privacy masking agreed in advance, and supports the platform after go-live.
At a glance
| Question | Answer |
|---|---|
| What it records | Screens, user actions, network requests, errors and crashes, from real devices |
| Platforms | Native Android and iOS, Flutter, React Native and Kotlin Multiplatform; Datadog also lists SDKs for .NET MAUI and Unity |
| What it measures | Mobile Vitals such as slow renders, frozen frames, crash-free sessions by version, memory and CPU |
| Privacy | Mobile Session Replay masks all text, inputs and images by default; touches are hidden by default |
| Where the data goes | To your Datadog site; as of November 2026 Datadog lists no site in the Middle East |
| What Interkey does | Licences, SDK set-up, privacy rules, backend links, release dashboards and support |
What mobile app monitoring has to catch
For a bank, a telecom operator or a government service in the Kingdom, the app is often the main way customers reach you. When it fails, people do not file a ticket; they call, visit a branch or leave a one-star review. A useful set-up answers four questions quickly:
- Is it crashing, and for whom? Crashes and freezes grouped into issues, with the device model, OS version and app version behind each.
- Which screens are slow? Screen load times and slow or frozen frames, visible before reviews mention them.
- Is it the app or the API? The latency and errors of each network request, linked to the backend service that answered it.
- Did the last release help or hurt? Every figure above broken down by app version.
Store dashboards give part of this picture, late and without the backend view. Mobile app monitoring puts the device, the release and the API in one place.
Mobile application performance monitoring with Datadog RUM
Datadog RUM collects data from browser, mobile and TV applications. On mobile, these are the jobs it covers and where your team works on each.
| Job | What Datadog documents | Where you work |
|---|---|---|
| Crash reporting | Crashes grouped into issues; on Android also ANR (Application Not Responding) and NDK crashes in native C/C++ code; on iOS app hangs and watchdog terminations, both off by default | Error Tracking |
| Readable stack traces | Deobfuscated Android crash reports with stack trace mapping; iOS stack traces symbolicated from uploaded .dSYM files | Error Tracking |
| Slow and frozen screens | Mobile Vitals: refresh rate, slow renders, frozen frames, CPU ticks per second and memory utilisation; hang rate on iOS | RUM, Mobile Vitals |
| API latency | Each network request the app makes is recorded as a resource; with tracing headers on chosen hosts, it links to the backend trace | RUM Explorer, APM |
| Release health | Crash-free sessions by version, and every RUM figure filterable by app version | RUM, Mobile Vitals |
| What the user saw | Mobile Session Replay for native Android and iOS, Kotlin Multiplatform, React Native and Flutter (Flutter listed as Preview) | Session Replay |
iOS, Android, Flutter and React Native app monitoring
Each platform has its own SDK, and each has one step teams forget: making crash reports readable.
iOS app monitoring
To turn iOS crash reports from memory addresses into file names and line numbers, each build's .dSYM files are uploaded to Datadog with its datadog-ci tool. App hang and watchdog termination reporting are switched on in the RUM configuration. Interkey adds the upload to your build pipeline so it runs on every release.
Read more
Android app monitoring
The Android SDK adds ANR reporting and native C/C++ crash reporting. Release builds are usually obfuscated, so mapping files are uploaded with each build. Datadog's network interceptor takes the hosts that should receive tracing headers, which is how a slow request on the phone leads to the trace on your servers.
Flutter and React Native monitoring
Cross-platform apps use Datadog's Flutter or React Native SDK, built on the native ones. Crashes can come from shared code or the native layer, so both sets of symbol files belong in the pipeline. We confirm feature support for your framework version during scoping.
Mobile RUM is one part of Datadog Real User Monitoring; a web portal can be covered by the same set-up.
RelatedDatadog Real User Monitoring
Privacy masking in Mobile Session Replay
A replay of a banking or government app can show names, balances and ID numbers. Datadog provides masking levels for mobile; choosing them is part of the design, agreed with your data protection officer.
| Setting | Options | Default |
|---|---|---|
| Text and input | mask_all, mask_sensitive_inputs (passwords, emails, phone numbers), mask_all_inputs | mask_all |
| Images | mask_all, mask_none; plus mask_large_only on Android and mask_non_bundled_only on iOS | mask_all |
| Touches | hide, show | hide |
| Per view | Overrides for text, images and touches, or a "Hidden" label that skips a view and its children | Inherited from the nearest parent view |
Replay masking covers what is on screen, not a national ID or mobile number inside a request URL or error message. On Android, event mappers can change attributes such as URLs and error messages before events are batched; our guide to masking personal data in telemetry explains how we test such rules against Saudi formats.
Two more settings decide what leaves the phone. Tracking consent in the Android and iOS SDKs is pending, granted or not granted: while pending, data is batched on the device but not sent; if refused, the batch is wiped. The session sample rate sets the share of sessions sent. RUM data is stored on your Datadog site, and as of November 2026 none is in the Middle East; read our observability data residency guide before deciding what may be recorded.
Banking, telecom and government apps
The same tool is used differently by each kind of organisation:
- Banking and payments. Sign-in, transfer and card screens are watched release by release. Replays stay masked, and only screens your compliance team approves are unmasked, if any.
- Telecom. Self-service apps for recharges, bundles and bills run on a very wide range of devices. Mobile Vitals by device model show which handsets struggle.
- Government services. Journeys such as national single sign-on, applications and appointment booking are measured end to end, with RUM linked to Datadog APM so a slow step points to the service behind it.
RUM shows what real users met. For journeys that must be tested even when nobody is using them, add synthetic monitoring.
Relatedsynthetic monitoring
What Interkey delivers
- Datadog licences, sized on expected session volume and quoted with the set-up and support.
- SDK set-up in your iOS, Android, Flutter or React Native code, tagged with the same service, environment and version names as your backend.
- Crash symbol uploads in your build pipeline for every release.
- Privacy rules: masking levels, per-view overrides, event rules and the consent setting.
- Release dashboards and alerts for crash-free sessions, slow screens and API errors.
- Technical support from Riyadh, in Arabic and English, or a documented handover.
How a mobile monitoring project runs
-
Choose apps and journeys.
Which apps and platforms, and which journeys matter most.
-
Agree the privacy design.
Masking levels, screens that stay hidden, event rules and consent, signed off before any SDK ships.
-
Instrument a test build.
SDKs and symbol uploads checked in a test build.
-
Link to the backend.
Tracing headers on your own API hosts, so requests connect to traces in Datadog APM.
-
Release through the stores.
The instrumented version goes out on your normal release cycle, including store review.
-
Dashboards, alerts and tuning.
Release comparisons, alerts and sampling tuned on real traffic.
-
Operate or hand over.
Interkey supports the platform, or hands it over with documentation.
What drives the cost
Datadog prices RUM per 1,000 sessions, and Session Replay is priced separately from RUM itself. The drivers are monthly sessions across your apps, how many you keep for investigation and how many you replay. Retention filters and the sample rate are the main levers, and can keep the sessions that matter, such as those with crashes. Datadog's published list prices and how they combine are on our Datadog pricing page.
Questions buyers ask
Which mobile frameworks can be monitored besides native iOS and Android?
Datadog lists SDKs for Flutter, React Native, Kotlin Multiplatform, .NET MAUI and Unity. Feature support differs by framework and SDK version, so we confirm it during scoping.
Can we compare crash rates between app releases?
Yes. Mobile Vitals include crash-free sessions by version, and crashes, slow screens and API errors can all be filtered by app version, so a new release can be compared with the previous one.
How do we keep national ID and mobile numbers out of session replays and crash reports?
Keep the default masking, which hides all text, inputs and images, and unmask only approved screens. Values inside URLs and error messages need separate event rules, which we test against Saudi ID and mobile formats before go-live.
Does mobile monitoring data leave Saudi Arabia?
Yes, data you send goes to your Datadog site, and as of November 2026 none is in the Middle East. Masking, event rules, consent and sampling decide what leaves the phone; our data residency guide sets out the options.
How is mobile app monitoring licensed, and what moves the cost?
Datadog prices RUM per 1,000 sessions, with Session Replay priced separately. Session volume, retention filters and the sample rate move the cost most. Interkey quotes the licences, the set-up and support together.
How long does it take to instrument an existing banking or government app?
It depends on the number of apps and frameworks, the privacy sign-off and your store release cycle. We give an estimate after a short scoping call, and support from Riyadh continues after go-live.
Next
Read next
Next step
Plan mobile app monitoring
Tell us which apps you want to monitor, their platforms or frameworks, roughly how many sessions they see each month, and whether Datadog already runs on your backend. We can quote the Datadog licences, the set-up and technical support together.
Or directly
+966-11-2180999 [email protected]Tawuniya Towers, North Tower, 7th Floor, King Fahad Highway, Olaya, P.O. Box 56835, Riyadh 11564, Saudi Arabia