Mobile App Performance Monitoring in Production

We've encountered situations where an app in App Store receives complaints about scrolling stutters, even though everything runs smoothly in the simulator. The user won't send you an allocation profile, and you can't run Xcode Instruments in CI. Production performance monitoring is a separate discipline: tools must work on the device, not impact UX, and send aggregated metrics. Our experience shows that systematic monitoring reduces crash rate by 30% in the first month and increases retention by 5%. Over 10 years, we've implemented monitoring for 50+ mobile apps with audiences starting at 100k DAU.

Why Production Performance Monitoring Is Critical

In lab conditions it's easy to measure FPS over an ideal network. In production, you have thousands of device configurations, OS versions, battery states, background load. Only real-user monitoring gives objective p50/p95/p99 metrics. For example, average cold start time on iPhone 12 might be 1.2 s, while on Samsung Galaxy A10 it's 4.5 s. Without production monitoring, you won't see that. Moreover, tracking performance in a live environment uncovers issues that don't reproduce on test devices: race conditions, memory leaks under load, multithreading problems on different CPUs.

Which Metrics to Monitor for User Retention

Scroll FPS is one of the main indicators of perceived performance. For example, UITableView jerks due to synchronous JPEG decoding on the main thread are a classic. We measure via CADisplayLink and send p5 (percentage of frames below 60 FPS).

How to Measure Scroll FPS

Step-by-step for iOS:

1. Create a CADisplayLink and add it to the main run loop.
2. Count frames per second.
3. Send the metric with the screen name.

class FPSMonitor {
    private var displayLink: CADisplayLink?
    private var lastTimestamp: CFTimeInterval = 0
    private var frameCount = 0

    func start() {
        displayLink = CADisplayLink(target: self, selector: #selector(tick))
        displayLink?.add(to: .main, forMode: .common)
    }

    @objc private func tick(_ link: CADisplayLink) {
        frameCount += 1
        if link.timestamp - lastTimestamp >= 1.0 {
            let fps = Double(frameCount) / (link.timestamp - lastTimestamp)
            MetricsCollector.record("screen_fps", value: fps, screen: currentScreen)
            frameCount = 0
            lastTimestamp = link.timestamp
        }
    }
}

On Android we use FrameMetricsAggregator from androidx.core — it provides breakdown by rendering phases. It's important to collect p5 (bottom 5% of frames), as average FPS can mask rare hitches.

Memory warnings — iOS sends didReceiveMemoryWarning before force-closing the app. Log this event with the current screen and memory usage via task_info. On Android, the analog is ActivityManager.getMemoryInfo and logging fragments. ANR on Android is another critical metric: if its rate exceeds 0.1%, it signals immediate main thread optimization. Read more about ANR.

Which Monitoring Tool to Choose?

Compare three popular solutions:

Firebase Performance — zero entry threshold. The SDK automatically collects cold start time, HTTP requests (latency, response size), screen rendering. Add custom traces for business logic:

let trace = Performance.startTrace(name: "catalog_load")
trace.start()
catalogService.load { [weak self] result in
    trace.stop()
    self?.handleResult(result)
}

val trace = Firebase.performance.newTrace("catalog_load")
trace.start()
catalogRepository.load { result ->
    trace.stop()
    handleResult(result)
}

Sentry Performance — if you already use Sentry for crash tracking, enabling Performance doesn't require a new SDK. Excellent for distributed tracing: you see not only client side latency but also backend request breakdown. Datadog RUM — the choice for teams with an existing Datadog infrastructure. It automatically records Session Replay (video of interactions), FPS, network requests with full stack trace. Our experience integrating Datadog RUM on a project with 500k DAU reduced problem search time from 2 hours to 10 minutes.

How to Configure Alerts to Avoid False Positives

It's important not to overload the team with false alarms. Recommended thresholds:

Set up alerts in Firebase Performance or Datadog on these thresholds with notifications to Slack/Telegram. Alert fatigue is the main enemy: don't set thresholds too low. Start with p99 and gradually increase sensitivity. Ensure alerts contain enough context (app version, device model, OS version) for quick problem identification.

What's Included in the Work

We offer integration of one SDK — Firebase Performance, Sentry Performance, or Datadog RUM — within 1–3 days. We add custom traces for key operations, FPS monitoring, memory warnings, and configure alerts with notifications to Slack/Telegram. Full dashboard with metrics — up to 5 days. Cost is calculated individually. Contact us to select the tool — we'll help you choose the optimal option and set up monitoring end-to-end. We guarantee a 30% crash rate reduction in the first month.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

• Development and approval of a tracking plan with product and marketing teams.
• SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
• Setup of funnels, cohorts, dashboards, and alerts.
• Automation of symbolication and .dSYM upload via Fastlane.
• Documentation of events and parameters.
• Team training on the analytics platform.
• Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.