Flutter Authorization with RLS

Summary

This tutorial extends a Flutter real-time chat app by adding authorization and one-to-one conversations backed by Supabase. It introduces a rooms page for starting conversations and listing existing rooms, while flutter_bloc coordinates profile and message data across the rooms and chats pages. The database changes add rooms and room_participants tables, connect messages to rooms, expose create_new_room for reusing or creating a two-user room, and register deep links for email confirmation on iOS and Android. SQL RLS policies then restrict room, participant, and message reads to participants and require message inserts to use the caller's profile ID, producing a real-time chat app with authentication and authorization.

Takeaways

1. 1

   The is_room_participant SQL function checks whether auth.uid() belongs to a specified room and is reused by RLS policies.

2. 2

   The messages table receives a room_id foreign key, while room_participants relates profiles to rooms with a composite primary key.

3. 3

   The article notes that injecting the Supabase instance into the cubit would make bloc_test-based testing possible, and suggests Supabase Presence for showing users who are online.