Skip to main content
Recorded playback becomes available after a room finishes broadcasting and the backend publishes recorded playback metadata. The social.plus SDK owns room status, recorded playback URLs, recorded thumbnails, and recorded resolution metadata. Your app owns the actual player, queueing, seek controls, buffering, and retry UI.
This page covers SDK-recorded playback data. AVPlayer, ExoPlayer, HLS.js, browser autoplay handling, DRM, captions, and player UI are app-owned concerns after the SDK returns a recorded playback URL.

Platform Surface

Parameters

Wait for Recorded Status

Observe the room while the playback screen is open. Treat ended as a processing state and only hand a recorded URL to your player after the room status becomes recorded.

Read Recorded Sources

Recorded metadata can contain more than one playback item. Preserve the SDK order unless your product has a backend-defined reason to reorder segments.

Refresh a Playback URL

Refresh recorded playback data before starting playback, after a long pause, or when your player reports an expired or unauthorized media URL.

Status Handling

Do not treat ended as playable recorded content. Wait for recorded status or a successful platform URL refresh response before handing a recorded URL to the player.

Segment and Player Boundary

Multiple recorded playback items can represent multiple files for one recording. Preserve the SDK order and let the player layer decide whether to play only the first URL or queue all URLs.

Live Room Viewing

Discover room posts, observe live rooms, and choose playback sources.

Start Broadcasting

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

Manage Rooms

Observe, query, update, stop, or delete room records.