Content delivery

Content delivery covers how your app chooses where content opens and what content loads.

How delivery fits together

1. Player source: the entry point in your app (widget, Moments tabs, entry point, Moments container, or delegate-driven open).
2. Data source: what the SDK loads for that entry point (Labels, Content IDs, Recommendations, free text, or Composite when you need more than one source in one feed).
3. Ordering and limits: how results are sorted and how many items return.
4. Display surface: widgets and related UI that preview content before the player opens.

Supporting topics (labels as a mechanism, delivery for Videos, and delegates) sit beside that spine. They do not replace the four steps. For how widgets look, see Widget appearance.

Topics in this section

Follow the delivery path first:

• Player sources: where content opens
• Data sources: what loads (including Composite)
• Ordering and item limits: sort and caps (under Data sources)
• Widgets and CMS-configured widgets: preview surfaces
• Moments tabs: multi-feed player surface

Then supporting topics:

• Labels mechanism
• Delivering Videos
• Live streaming
• Delegates
• Videos - multi-aspect ratio support
• Widget appearance
• CMS widget builder (CMS workflow)