Prompt
Supabase auth is fine but I need better push notifications
Latest observation
Nov 11, 2026
OpenAI APIWeb search: off
Got it — if Supabase Auth is already working, the next step is usually to add a dedicated push notification service rather than trying to force auth to do notifications.
A good setup depends on your app, but here are the common options:
Best options for push notifications
- Firebase Cloud Messaging (FCM)
Best general choice for Android, web, and often iOS when paired with APNs. - OneSignal
Easiest to set up, good dashboards, segmentation, and cross-platform support. - Expo Notifications
Best if you’re using React Native + Expo. - Apple Push Notification service (APNs)
Required for native iOS delivery, usually used through Firebase or another provider.
Recommended architecture with Supabase
Use Supabase for:
- user auth
- storing device tokens
- notification preferences
- sending notification triggers from Edge Functions or server-side jobs
Use a push provider for:
- actual delivery to devices
Typical flow
- User logs in with Supabase Auth
- App registers device with FCM/OneSignal/APNs
- Device token is saved in Supabase
- Backend event happens
- Supabase Edge Function or backend sends the push notification via provider API
If you want the easiest path
- React Native / Expo: use Expo Notifications
- Web + mobile with minimal setup: use OneSignal
- More control / scalable infrastructure: use FCM
If you want, I can help you design the exact setup for your stack — for example:
- Supabase + Next.js
- Supabase + React Native
- Supabase + Flutter
- Supabase + Expo
If you tell me your app stack, I’ll suggest the best push notification approach and a simple implementation plan.