# App stability at scale with a layered defense

DevFeed: [App stability at scale with a layered defense](<https://devfeed.tech/articles/app-stability-at-scale-with-a-layered-defense-91299.md>)

Original publisher: [Read original article](<https://engineering.grab.com/app-stability-at-scale-with-a-layered-defense>)

Author: Nguyen Van Minh

Published: 2026-10-21T00:23:00Z

Content type: article

Language: en

Sources: [Grab Tech](<https://devfeed.tech/sources/grab-tech.md>)

Topics: [mobile-app-performance](<https://devfeed.tech/topics/mobile-app-performance.md>), [mobile devops](<https://devfeed.tech/topics/mobile-devops.md>), [Crashlytics](<https://devfeed.tech/topics/crashlytics.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Android](<https://devfeed.tech/topics/android.md>), [Firebase](<https://devfeed.tech/topics/firebase.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [appstores](<https://devfeed.tech/topics/appstores.md>), [Google Play](<https://devfeed.tech/topics/google-play.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding-assistants](<https://devfeed.tech/tags/ai-coding-assistants.md>), [android](<https://devfeed.tech/tags/android.md>), [app](<https://devfeed.tech/tags/app.md>), [app-stability](<https://devfeed.tech/tags/app-stability.md>), [artificial-intelligence](<https://devfeed.tech/tags/artificial-intelligence.md>), [artificial-intelligence-ai](<https://devfeed.tech/tags/artificial-intelligence-ai.md>), [code](<https://devfeed.tech/tags/code.md>), [coding-assistants](<https://devfeed.tech/tags/coding-assistants.md>), [crash](<https://devfeed.tech/tags/crash.md>), [crashes](<https://devfeed.tech/tags/crashes.md>), [debug](<https://devfeed.tech/tags/debug.md>), [defense](<https://devfeed.tech/tags/defense.md>), [devices](<https://devfeed.tech/tags/devices.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [flag](<https://devfeed.tech/tags/flag.md>), [google-play](<https://devfeed.tech/tags/google-play.md>), [hotfix](<https://devfeed.tech/tags/hotfix.md>), [ios](<https://devfeed.tech/tags/ios.md>), [merge](<https://devfeed.tech/tags/merge.md>), [metadata](<https://devfeed.tech/tags/metadata.md>), [mobile](<https://devfeed.tech/tags/mobile.md>), [reliability](<https://devfeed.tech/tags/reliability.md>), [scale](<https://devfeed.tech/tags/scale.md>)

## AI overview

Grab manages mobile crash risk with layered checks that catch problems earlier and limit their impact. Android Lint and SwiftLint run on every merge request, blocking new high-severity findings; tests, QA, and a mandatory one-week Grab Early Access period catch runtime issues before production. Releases then expand through a monitored week-long staged rollout that can pause automatically, while feature flags allow gradual activation and instant shutdown. In production, crash-rate thresholds and trend alerts notify on-call engineers, who prioritize disabling a flag, applying a server-side fix, or shipping a hotfix followed by a post-mortem. Automated ticketing routes actionable crashes by severity. For hard-to-diagnose cases, Crashlytics data is exported to BigQuery for SQL analysis and dashboards, and sessions include metadata such as last screen, install source, and navigation history. Some environmental crashes are monitored and contained rather than treated as code defects.

## Source excerpt

Introduction Artificial intelligence (AI) coding assistants have changed how fast we can ship. They have not changed how mobile users experience a crash. That gap is the pressure every mobile stability program now operates under. The Grab superapp, which millions of users across Southeast Asia use to book rides, order food, and more, operates at a large scale. On Android alone, it spans millions of lines of code, with many engineers shipping code into every release on a weekly release cycle. Maintaining app stability is not just a technical goal; it is a product commitment to those users. With the rise of AI coding assistance, the volume of change in every release has grown, and so has the number of ways a single change can break something in an already large codebase. At this scale, crashes leaking into production are an ongoing risk. A high volume of merge requests lands every week across many product teams, many shipping features behind flags that are switched on independently of releases. Any one of those changes can introduce a crash. Most of the time, the stack trace points straight to the responsible change and team. The hard cases are the exceptions: crashes without a usable stack trace, such as native crashes without debug symbols, where finding the cause means cross-referencing release timelines, flag rollouts, and session metadata. The cost of a crash is also steeper on mobile than on the web. A web fix can go live in minutes; a mobile crash that ships stays on users' devices. With more than 100 million downloads on Google Play as of October 2026, not every user has auto-update enabled, and until a force update reaches them, some will run a broken version for months. Meanwhile, the crash degrades their experience, drags down the crash-free session rate, and can hurt the app's ranking on Google Play. If it is severe enough to need a hotfix, the team also has to prepare an out-of-cycle build, pulling time away from planned work. We keep the Grab superapp st