Convex component for Expo push notifications with built-in retry logic, batching, and delivery tracking to eliminate notification failures.
npm install @convex-dev/expo-push-notificationsThis is a Convex component that integrates with [Expo's push notification API](https://docs.expo.dev/push-notifications/overview/) to allow sending mobile push notifications to users of your app. It will batch calls to Expo's API and handle retrying delivery.
The Expo Push Notifications component provides automatic retry logic with exponential backoff for failed notifications. It handles network errors, rate limiting, and service unavailability by queuing failed notifications and retrying them intelligently.
This component automatically batches up to 100 push notifications into single API requests to Expo's servers. It optimizes delivery by grouping notifications and handling partial failures within batches, reducing your API usage and improving performance.
The component automatically detects and handles expired or invalid Expo push tokens by parsing error responses. It provides hooks to remove invalid tokens from your database and prevent future delivery attempts to dead endpoints.
Built-in delivery tracking captures receipts from Expo's service to monitor notification success rates. The component stores delivery status and error details, enabling you to debug failed notifications and maintain notification analytics.
Yes, the Expo Push Notifications component automatically handles rate limiting from Expo's servers. It implements exponential backoff and queues notifications when rate limits are hit, ensuring all notifications are eventually delivered without losing messages.
The Expo Push Notifications component provides configurable retry parameters including maximum retry attempts, backoff intervals, and error handling strategies. You can customize these settings when initializing the component to match your application's requirements.
The component intelligently groups notifications with similar content and delivery parameters into batches of up to 100. Each notification can have unique recipients and custom data while still benefiting from batched delivery to reduce API calls to Expo's servers.
The Expo Push Notifications component queues notifications in your Convex database when Expo's service is unavailable. It automatically retries delivery once the service recovers, ensuring no notifications are lost during outages or maintenance windows.