Crash monitoring catches crashes. The OTA releases that hurt most are the ones that don't crash: a checkout button that stops working, a sign-up flow that silently fails. Crash-free sessions stay at 100% while revenue drops.
Here's how to make every over-the-air release prove itself on your business metrics before it reaches everyone, using Healkite (CodePush-compatible).
1. Track the event that matters
import { trackEvent } from "react-native-healkite"; trackEvent("checkout_success"); 2. Release with a guard on it
npx healkite release -p ios -r 4.2.0 --guarded --guard-metric checkout_success:20 The release goes to 1% → 10% → 50% → 100%. At each step Healkite compares checkout_success per session with the previous release and waits until it has enough sessions to judge. If it falls more than 20%, the release stops and phones go back to the last good version.
3. Keep the on-device safety net
A new bundle's first launch is a trial: if it never reaches your first screen, the next launch runs the previous bundle. No server needed.
Moving from App Center CodePush
- import codePush from "react-native-code-push"; + import codePush from "react-native-healkite/codepush"; Full guide: https://docs.healkite.com/guarded-rollouts · Migrating: https://docs.healkite.com/migrate-from-codepush