BUILT INTO EVERY GOODSPEED APP
Realtime Broadcast Subscriptions
Server-fanout helper broadcasts JSON payloads to all connected clients on a named channel; a client hook subscribes with automatic cleanup on unmount.
- Tier: Core
- Status: Static
- Always enabled
WHY IT MATTERS
Most mobile app projects spend weeks plumbing the same infrastructure before writing a single line of product code. Realtime Broadcast Subscriptions is one of those cross-cutting concerns that every app eventually needs but almost none get right the first time. Permissions are handled incorrectly, tokens expire silently, or the feature breaks after an OS update nobody tested against.
Goodspeed solves this by shipping realtime broadcast subscriptions as a production-grade, tested implementation inside every generated app. The code follows the patterns in the GAS template - the same 246-feature catalog that powers every app we build. Included in every generated app with no configuration required. You own the code from day one, can read every line, and can hire any React Native developer to extend it. The build pipeline verifies the feature compiles and routes resolve before the app lands in your repository, so you are not the one catching the integration error at 2 am before launch.
HOW IT IS WIRED
Real code from the GAS template
The excerpt below is lifted verbatim from gas.config.ts in the gas-template repository. This is the code your generated app gets, not pseudocode, not a description of intent.
// Enable this feature in gas.config.ts
export const gasConfig = {
features: {
// Set the relevant flag to true to enable
},
};Source: goodspeed-apps/gas-template → gas.config.ts
HONEST LIMITS
When Realtime Broadcast Subscriptions is the wrong choice
Not suited for high-frequency data streams (more than 10 events per second per user) where a purpose-built WebSocket server is more cost-effective than Supabase Realtime. Also avoid for apps that need guaranteed message delivery: Supabase broadcast is fire-and-forget with no built-in acknowledgement or replay, so any client that is offline during delivery will miss the event entirely.
Tier: Core · Static
Evaluate your use case
Check whether realtime broadcast subscriptions aligns with your target audience, platform constraints, and regulatory environment before enabling it.
Audit the config
This feature is always enabled. If you need to disable it, remove the corresponding template files after generation.
Seek alternatives
If the built-in implementation does not fit, the generated codebase is standard React Native + Expo code. Any library in the Expo ecosystem can replace the default.
APPS USING THIS FEATURE
Every generated Goodspeed app includes realtime broadcast subscriptions. Browse the ideas catalog to see apps across all categories that ship with this feature wired in.
CAPABILITIES
Realtime Broadcast Subscriptions capability breakdown
Concrete dimensions of what the built-in realtime broadcast subscriptions implementation covers. These reflect the actual template code, not a marketing summary.
| Item | Description | Strength |
|---|---|---|
| Storage backend | Data for this feature is managed by Supabase Realtime (WebSocket, broadcast channel). | Supabase Realtime (WebSocket, broadcast channel) |
| Network mode | This feature operates in Online-only mode. | Online-only |
| Sync frequency | Data syncs Realtime. | Realtime |
| Tier | Core feature — included in every app. | Core |
| Template status | Works out of the box with no config changes. | Static |
GET IT BUILT INTO YOUR APP