การสมัครรับข้อมูลแบบเรียลไทม์

Real-time subscriptions allow your React Native app to receive database changes as they happen, without polling. When another user inserts, updates, or deletes a row, Supabase pushes the change to all subscribed clients over a WebSocket connection.

This is ideal for chat apps, live feeds, collaborative tools, and any feature where multiple users interact with shared data. Supabase's real-time engine is built on PostgreSQL's logical replication and the supabase-js client handles the WebSocket lifecycle for you.

Before subscribing to changes, you must enable real-time replication for the table in Supabase. Go to the Supabase dashboard, open Database > Replication, and add the table to the supabase_realtime publication.

You can also do this with SQL: ALTER PUBLICATION supabase_realtime ADD TABLE your_table;. Without this step, your subscription will connect but receive no events, which is a common source of confusion when first setting up real-time.

Subscriptions in Supabase v2 are created with supabase.channel('channel-name'). You attach one or more event listeners with .on('postgres_changes', filter, callback), then call .subscribe() to start the WebSocket connection.

The filter object specifies the event (INSERT, UPDATE, DELETE, or * for all), the schema, and the table. The callback receives a payload object with the changed data.

The payload object passed to your callback contains the change details:

• eventType — 'INSERT', 'UPDATE', or 'DELETE'
• new — the new row data (available for INSERT and UPDATE)
• old — the previous row data (available for UPDATE and DELETE)
• schema and table — which table changed

For DELETE events, payload.new is an empty object and payload.old contains the deleted row. For INSERT, payload.old is empty.

The most common pattern is to update a state array when a real-time event arrives. For INSERT events, append the new row. For UPDATE, replace the matching row. For DELETE, filter the row out.

Be careful to use the functional form of the state setter (setMessages(prev => [...])) to always work with the latest state, since the subscription callback is a closure that captures the state at subscription time.

To subscribe only to changes in rows relevant to the current user or room, add a filter string to the event options. The filter syntax is 'column_name=eq.value', similar to PostgREST query syntax.

This reduces unnecessary network traffic on the client and avoids processing changes that are not relevant to the current screen. For example, in a chat app, subscribe only to messages in the current room.

Supabase channels also support Broadcast, which lets you send ephemeral messages to all clients subscribed to the same channel without writing to the database. This is perfect for typing indicators, cursor positions, or transient presence events.

Use .on('broadcast', { event: 'typing' }, callback) to receive broadcast messages and channel.send to send them. Broadcast messages are not stored and do not trigger RLS policies.

Presence is a Supabase feature that lets you track which users are currently online and share state between them. Each client tracks its own presence, and the channel aggregates the presence of all connected clients in real time.

This is ideal for showing an online indicator next to user avatars in a chat list or a participants sidebar in a collaborative document.

Real-time channels use WebSocket connections. It is critical to clean up by calling supabase.removeChannel(channel) when the component unmounts. If you forget to clean up, you will accumulate WebSocket connections and leak memory.

Return a cleanup function from useEffect that removes the channel. React calls this cleanup automatically when the component unmounts or before the effect re-runs due to dependency changes.

A real-time chat screen combines an initial useEffect fetch for existing messages with a real-time subscription for new ones. Fetch the last 50 messages on mount, then append new messages as they arrive via INSERT events.

Use an inverted FlatList (inverted prop) so the newest message always appears at the bottom without needing to scroll. Render each message as a row with the sender's avatar and text.

The .subscribe() method accepts an optional callback that receives the subscription status. You can use this to show connection indicators in your UI or retry logic when the subscription fails.

Possible status values include 'SUBSCRIBED' (active), 'TIMED_OUT', 'CLOSED', and 'CHANNEL_ERROR'. Always handle error states to give users feedback when real-time functionality is unavailable.

Test your understanding of React Native Mobile Development concepts from this lesson.

In this lesson you learned: how to subscribe to Postgres changes with supabase.channel, how to filter subscriptions by column value for targeted updates, and how to properly clean up channels on component unmount to avoid WebSocket leaks. Next up we explore integrating Firebase Auth and Firestore as an alternative backend for React Native apps.