RORK LABJP
PLAY — Google Play's target API level 36 requirement took effect yesterday, August 31. From today, new apps and updates must target Android 16VISIBILITY — Apps still on API 35 stay listed but disappear for users on newer Android versions. No error is raised; new installs simply fade, which makes the change easy to missEXTENSION — If you missed the deadline, an extension through November 1, 2026 can be requested in Play Console — best filed alongside a concrete migration planAPPLE — On the Apple side, the event lands September 9 and iOS 27 is reported to ship September 14. Testing generated apps on iOS 27 hardware before release week is time well spentEXPO — Expo released expo-paste-input on August 28, a native module that brings image, GIF, and sticker paste to React Native TextInputEAS — EAS Observe reached general availability on August 20, putting crash and performance monitoring on the same EAS platform as builds and updatesPLAY — Google Play's target API level 36 requirement took effect yesterday, August 31. From today, new apps and updates must target Android 16VISIBILITY — Apps still on API 35 stay listed but disappear for users on newer Android versions. No error is raised; new installs simply fade, which makes the change easy to missEXTENSION — If you missed the deadline, an extension through November 1, 2026 can be requested in Play Console — best filed alongside a concrete migration planAPPLE — On the Apple side, the event lands September 9 and iOS 27 is reported to ship September 14. Testing generated apps on iOS 27 hardware before release week is time well spentEXPO — Expo released expo-paste-input on August 28, a native module that brings image, GIF, and sticker paste to React Native TextInputEAS — EAS Observe reached general availability on August 20, putting crash and performance monitoring on the same EAS platform as builds and updates
Articles/Dev Tools
Dev Tools/2026-05-21Advanced

Automating Production Incident Response as a Solo Developer — Crashlytics, Sentry, Slack Routing, and Staged Rollback

Twelve years of running my own iPhone and Android apps, accumulating 50 million downloads, taught me a specific shape for production incident response. This article shares the Crashlytics + Sentry double layer, Slack routing into interrupt and log channels, and a Remote Config plus EAS Update staged rollback I keep returning to.

Rork548Crashlytics12Sentry6Slack2Remote Config10Incident ResponseArchitecture22Indie Developer11AdMob70

Premium Article

Who Notices When AdMob Revenue Drops at 2 a.m.?

I have been shipping iPhone and Android apps as a solo developer since 2014. The catalog has crossed 50 million cumulative downloads, but I still receive every production alert by myself. There is no team, no on-call rotation. The night AdMob eCPM halved at 1 a.m., the night Crashlytics Fatals spiked at 2:30, the night a paywall change wiped purchases — all of those happened with me asleep.

For the first several years my pattern was the same: wake up, see the revenue dip, scramble to edit Remote Config with bleary eyes. Editing live production values half-awake is a way to cause a second incident, and I have caused several. Step by step I built scaffolding around the late-night hours, and the system now usually lands at one specific state by sunrise: a stage-one rollback has already executed automatically, leaving me a calmer surface to inspect at breakfast.

This article walks through the architecture and code behind that scaffolding. It is not the incident response material from team-oriented SRE books; it is what one person can realistically maintain.

Three Layers of Detection I Settled On After 12 Years

The first thing worth naming is that a single-layer alerting setup misses too much. I monitor three layers in parallel:

  1. Crash layer — the app exits, fails to launch, or always white-screens on one route.
  2. Functional layer — the app does not crash, but purchase buttons do nothing, push delivery stalls, login fails silently.
  3. Revenue layer — eCPM collapses, purchase rate sags, churn spikes, or new install velocity drops.

Years ago, watching the crash layer alone was enough. Today, the functional and revenue layers cause more dollar-weighted damage. Crashlytics can sit at zero Fatals while AdMob eCPM is sixty percent below yesterday — that day's revenue is gone regardless. Three layers, three different notification policies, three different escalation paths.

LayerPrimary signalSecondary signalNotification priority
CrashFirebase CrashlyticsSentryCritical, immediate
FunctionalSentry (errors + performance)Firebase PerformanceHigh, within 5 minutes
RevenueAdMob API + RevenueCatFirebase AnalyticsMedium, within 30 minutes

"Sending the same data to two services" looked wasteful for a long time, but the cost of the redundancy is small compared to the cost of one missed Fatal during a release. I now treat the double instrumentation as cheap insurance.

Thank you for reading this far.

Continue Reading

What follows includes implementation code, benchmarks, and practical content we hope you'll find useful. This site runs without ads — server and development costs are supported entirely by members like you. If it's been helpful, we'd be truly grateful for your support.

WHAT YOU'LL LEARN
A working pattern for binding Firebase Crashlytics issue cluster keys to Sentry fingerprints so the same crash collapses into one ticket across both services.
A Slack routing design that separates an interrupt channel (Critical, mentions allowed at night) from a log channel (silent, daytime triage), with the exact thresholds I use.
A Remote Config plus EAS Update rollback script that walks a feature down 100 → 50 → 10 → 0 percent with manual confirmation between stages, completing within five minutes.
Secure payment via Stripe · Cancel anytime

Unlock This Article

Get full access to the rest of this article. Buy once, read anytime. This site is ad-free — your support goes directly toward keeping it running.

or
Unlock all articles with Membership →
Share

Thank You for Reading

Rork Lab is ad-free, supported entirely by members like you. We publish practical guides daily with implementation code, benchmarks, and production-ready patterns. If you've found it useful, we'd love to have you on board.

  • Copy-paste ready implementation code
  • New advanced guides published daily
  • $5/mo or $15 for lifetime access
View Membership →

Related Articles

Dev Tools2026-05-19
Auto-Throttling AdMob When Crash Rates Spike: A Revenue-Protecting Brake Architecture with Rork, Firebase Remote Config, and Crashlytics
When crash rates spike, do you keep showing ads and watch your store rating crater, or pull back and accept the lost revenue? After 12 years of indie operations, my answer is neither: a four-state auto-throttle architecture that ties Firebase Remote Config and Crashlytics signals into AdMob serving decisions.
Dev Tools2026-07-24
Resolving App Config in Three Layers: Merging Defaults, User, and Remote With Bounded Overrides
A single type-safe layer that merges compiled defaults, user preferences, and remote config. So a broken remote value never takes your app down, each key gets its own override strength, plus schema validation and range clamping, built from a real production incident.
Dev Tools2026-06-12
Building a Developer Debug Menu Into Your Rork App — Verify Ads, Purchases, and Remote Config Before Release
A production-safe developer debug menu for Rork apps — switch environments, force test ads, simulate entitlements, and override Remote Config, with working TypeScript code and the pitfalls I hit running six apps.
📚RECOMMENDED BOOKS
Build a Large Language Model (From Scratch)
Sebastian Raschka
LLM Dev
Prompt Engineering for LLMs
Berryman & Ziegler
Prompting
AI Engineering
Chip Huyen
AI Eng
* Contains affiliate links
See all →