Weave Code
Laravel Expo Notifier Laravel Package
yieldstudio/laravel-expo-notifier
Send push notifications to Expo (React Native) apps from Laravel with a clean, fluent API. Manage Expo push tokens, send notifications to one or many devices, and integrate with Laravel's notification system.
Easily manage Expo notifications with Laravel. Support batched notifications.
Frequently asked questions about Laravel Expo Notifier
- How do I install yieldstudio/laravel-expo-notifier in a Laravel app?
- Install it with Composer using composer require yieldstudio/laravel-expo-notifier. Then follow the package setup for configuration and Expo credentials, and confirm the Laravel and PHP constraints in its composer.json. Because it is on a 0.0.x release line, pin the version you validate.
- Does laravel-expo-notifier integrate with Laravel's notification system?
- Yes, the package is designed around Laravel's notification system and a dedicated Expo notification channel. You typically create a notification class, build an Expo message, and send it to notifiable models. Check the README for the exact channel class and message API for version 0.0.17.
- Can I send Expo push notifications to multiple devices or batched tokens?
- Yes, the package supports sending notifications to one or many Expo push tokens and advertises batched notifications. Token management is part of the package scope, so you can store and select device tokens. For high volume, account for Expo rate limits and queue-based sending.
- Which Laravel and PHP versions are supported by laravel-expo-notifier?
- The provided context does not list exact Laravel and PHP version constraints. Check the package composer.json on GitHub or Packagist before adoption, then test against your application's Laravel and PHP versions. Since the package is pre-1.0, pin a version that passes your tests.
- Is yieldstudio/laravel-expo-notifier production ready?
- Treat it as pre-1.0 software: version 0.0.17 is a low-signal patch, so do not assume automatic upgrade safety. Use it in a non-critical notification path first, pin the version, review diffs, and wrap it behind an internal adapter. Add logging and alerting around send failures before broad production use.
- Does it handle Expo push receipts, invalid tokens, and retries?
- The overview mentions token management but does not confirm Expo receipt checking, invalid-token cleanup, or retry/backoff behavior. Review the source and README for receipt polling, error handling, and token pruning support. If those features are missing, build them in-house around queued sends and delivery monitoring.
- How do I configure Expo push credentials with this Laravel package?
- Expo push delivery may require an Expo access token depending on your project security settings, plus correct device push tokens. Configure credentials through the package config and environment variables rather than hardcoding them. Verify the exact config keys in the README for your pinned version.
- Can I queue Expo notifications sent from Laravel with this package?
- Laravel notifications can be queued, and this package sends through Expo's push API, so queue workers handle delivery asynchronously. Configure your queue driver and workers, then monitor failures and rate limits. For large audiences, use batched sends and consider receipt polling outside the request cycle.
- What are alternatives to laravel-expo-notifier for Laravel push notifications?
- Alternatives include calling the Expo push API directly, using Laravel notification channels for FCM or APNs, or adopting a provider-agnostic push service. This package fits best when your app standardizes on Expo managed workflow and you want Laravel-native message construction. If you need multi-provider abstraction or campaign orchestration, evaluate a broader service.
- How do I upgrade from 0.0.16 to 0.0.17 safely?
- Review PR #39 and the diff for ExpoMessage.php before upgrading from 0.0.16 to 0.0.17. Run package tests or add a smoke test for message payload construction, then validate in staging with representative Expo tokens. Keep the previous version pinned until delivery behavior is confirmed.
Weaver
How can I help you explore Laravel packages today?