💬
Get Help
alaa alsalami
alaa alsalami

Best Practice for Push Notifications with Supabase Backend in FlutterFlow

Integrations

I'm currently using Supabase as my backend for a FlutterFlow application and I need to implement push notifications. FlutterFlow's native push notification feature seems optimized for Firebase. I'm looking for the most efficient and stable solution to handle push notifications when using Supabase.

My core questions are:

  1. What is the recommended (best practice) approach for integrating push notifications (e.g., using Firebase Cloud Messaging (FCM), OneSignal, or a third-party service) while utilizing Supabase for user authentication and database?

  2. What is the optimal table structure in Supabase to store the necessary device tokens (FCM Token or similar) and notification logs?

Any detailed guides, community tutorials, or successful implementation examples would be highly appreciated.

What have you tried so far?

I've explored the initial FlutterFlow documentation, which primarily focuses on Firebase. I've read some community posts mentioning:

  • Using a Custom Action to retrieve the FCM token.

  • Storing the FCM token in a new column on the Supabase user profile table.

  • Using Supabase Edge Functions/Webhooks to trigger the notification send.

However, I'm seeking clarification on the most reliable and streamlined full-stack setup.

Did you check FlutterFlow's Documentation for this topic?
Yes
4