push-notifications

Push notifications in React Native require installing notification libraries, requesting user permissions, generating device tokens, and configuring a backend to send messages. For Expo apps, use expo-notifications with Expo's push service; for bare workflow, integrate Firebase Cloud Messaging. Both handle foreground and background delivery.

Yes. Expo managed workflow uses Expo's notification service by default for iOS and Android. Bare workflow apps can integrate Firebase Cloud Messaging directly. The Skill covers both paths with sample code for permission flows, token generation, and server-side message delivery.

Foreground notification handling requires subscribing to notification events in your app code. When a notification arrives while the app is active, your listener receives it before the system displays it, letting you show custom UI or trigger navigation instead of the default alert.

Server-side push delivery requires obtaining device push tokens from each client, then sending message payloads to Expo's API or Firebase Cloud Messaging with those tokens. The Skill includes example server payloads and backend integration patterns for both platforms.

iOS uses Apple Push Notification service (APNs) and Android uses Firebase Cloud Messaging, but Expo abstracts most platform differences. You request permissions once and use a unified token flow; Expo routes each platform's delivery automatically. The Skill covers permission requests and tap-driven navigation for both.

Unreliable delivery often stems from missing permission requests, incorrect token registration, improper background handling, or misconfigured server payloads. This Skill solves delivery by guiding permission flows, token generation, foreground/background event subscription, and validated server-side messaging patterns.