Skip to main content
Live room viewing starts from a room ID or a room post. The social.plus SDK owns room discovery, room status, live playback URLs, recorded playback metadata, and live room post collections. Your app owns the actual video player, buffering UI, autoplay policy, and platform playback SDK.
This page covers SDK room viewing data. AVPlayer, ExoPlayer, HLS.js, browser autoplay handling, DRM, and player UI are app-owned concerns after the SDK returns a playback URL.

Platform Surface

Parameters

Find Live Room Posts

Use live room post collections when your product shows a live shelf or a community-specific live section. Extract the roomId from room post data, then observe the room itself for playback state.

Observe Room Playback State

Observe the room record while the viewing screen is open. A live object update can move the UI from waiting, to live playback, to ended, and later to recorded playback.

Choose a Playback Source

Keep playback source selection small and deterministic. Pass the selected URL to your own player layer only when the SDK room state has a playable source.

Status Handling

If a room is live but the SDK returns no live playback URL, do not invent a fallback URL. Treat it as unavailable for the current viewer and show a product-specific blocked, unavailable, or retry state.

Player Boundary

Start Broadcasting

Fetch broadcaster credentials and start the host-side media session.

Manage Rooms

Observe, stop, update, or delete room records.

Recorded Playback

Handle recorded playback after a live room ends.