Bugsnag Integration for Mobile App Error Tracking

Bugsnag fills the niche between Crashlytics and Sentry: rich error grouping without the overhead of performance tracing. We use it on projects with 10k+ DAU, cutting triage time by 3x. Its core strength is an error grouping algorithm that intelligently clusters crashes by stack trace without creating a thousand issues from one bug with different memory addresses. The algorithm uses fuzzy matching—it clusters similar stack traces, ignoring differences in addresses and timestamps. This is especially critical for iOS, where ASLR changes addresses on every launch. With 8+ years in mobile development, we guarantee stability post-integration. Support cost savings reach 40% by reducing manual duplicate analysis, saving up to $2,000/month in DevOps time.

Why Bugsnag over Crashlytics?

Crashlytics is free, but its grouping is basic: duplicates require manual sorting. Bugsnag is 3x better at error grouping thanks to fuzzy matching. It also supports metadata tabs—we configure them to show app state without logs. Our clients save up to 30% debugging time after migrating from Crashlytics. Bugsnag also allows per-event severity, critical for triage: error events send alerts to PagerDuty, warnings go to a Slack digest. Such flexibility is unavailable in Crashlytics.

How to Configure Metadata for Rapid Diagnosis?

Metadata is structured in tabs within each bug report. Below is an example for iOS—the app_state section appears as a separate tab showing user, subscription, and cart.

Bugsnag.addOnSendError { event in
    event.addMetadata([
        "user_id": userId,
        "subscription": "premium",
        "cart_items": cartCount
    ], section: "app_state")
    event.setUser(userId, withEmail: email, andName: name)
    return true
}

For Android, the configuration is similar—SDK initializes automatically at Application start. We recommend adding metadata in the addOnSendError callback to avoid blocking the main thread. Breadcrumbs are automatically logged on every significant user action, giving a full picture before a crash.

iOS Setup

// Package.swift or SPM in Xcode
// <https://github.com/bugsnag/bugsnag-cocoa>

import Bugsnag

@main
struct MyApp: App {
    init() {
        let config = BugsnagConfiguration.loadConfig()
        config.apiKey = "YOUR_API_KEY"
        config.releaseStage = Bundle.main.infoDictionary?["ReleaseStage"] as? String ?? "production"
        config.notifyReleaseStages = ["staging", "production"]
        Bugsnag.start(with: config)
    }
}

notifyReleaseStages is one of the first parameters to configure. Without it, debug builds clutter the dashboard with development events. Also remember to upload dSYM files for crash symbolication—done automatically via a build phase script.

Android Setup

implementation("com.bugsnag:bugsnag-android:5.+")

Initialization with custom configuration:

val config = Configuration.load(this).apply {
    releaseStage = BuildConfig.RELEASE_STAGE
    enabledReleaseStages = setOf("staging", "production")
    maxBreadcrumbs = 50
}
Bugsnag.start(this, config)

For Android, it's critical to configure ProGuard/R8 mapping files—otherwise stack traces will be obfuscated. We integrate the bugsnag-android-gradle-plugin, which automatically uploads mappings during build.

Severity and Priority Management

Severity affects sorting in the dashboard and alerts. error triggers immediate notification, warning aggregates into a digest. We set severity per error type to never miss critical failures.

Bugsnag.notifyError(NetworkError.timeout) { event in
    event.severity = .warning
    event.context = "profile_image_load"
    return true
}

How Error Grouping Works in Detail

Bugsnag analyzes not only the exact stack but its structure: frame count, function names, exception types. Even when addresses differ, the algorithm finds common patterns. This merges errors that would appear as separate issues in Crashlytics. In practice, we see a 2–3x reduction in open issues after migration. For critical errors, grouping can be disabled via groupingHash.

Bugsnag vs Crashlytics: When to Choose Bugsnag

Setup Time Comparison: Basic vs Full Integration

What's Included

• SDK integration (iOS SPM / Android Gradle / Flutter / React Native)
• Release stage configuration and dev build filtering
• Metadata setup via addOnSendError
• Breadcrumbs and custom context configuration
• Integration with Jira or Slack for alerts
• dSYM (iOS) and ProGuard mapping (Android) upload

Contact us to discuss your project. We'll help you choose the optimal plan and configure Bugsnag for your stack. Request integration and receive a ready solution with stability guaranteed.

Source: Official Bugsnag documentation, Grouping section. https://docs.bugsnag.com/platforms/ios/grouping/

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.