Mobile SDK
A mobile SDK is the development kit that adds capabilities like live or short-form video into an iOS or Android app, so watching and paying happen without leaving it.
How does it differ from a web embed?
An embed puts a web view inside the app; an SDK becomes part of the app's own UI. That's why an SDK can reuse the app's signed-in state, push notifications, and payment methods — and support app-only behavior like PIP and native transitions.
What has to be integrated?
Member authentication, catalog and stock, payment methods, and push notifications, at minimum. Add the path that writes watch history back to the member account, or broadcast data can't inform the next purchase — and half the reason for embedding in the app disappears.
What do you check when adopting one?
Minimum supported OS versions, how much app size grows, release cadence, and the backward-compatibility policy. Unlike the web, app releases need review and user updates, so a fast-moving SDK version means a heavier operational load.
Three ways to add it to an app
Mobile SDK | Web embed | External link | |
|---|---|---|---|
Surface | Part of the app's UI | A web view inside the app | Leaves the app |
Signed-in state | Reuses the app account | Needs separate wiring | Usually breaks |
Payment | App payment methods | Via web checkout | External checkout |
PIP and push | Supported | Limited | Not available |
Adoption cost | App release and review | Relatively light | Lightest |
Frequently Asked Questions
Q. Can you use an SDK without an app?
A mobile SDK presupposes one. With web only, a web SDK or embed adds the same capability — and when the app arrives later, the same broadcast can serve both.
Q. How long does implementation take?
It depends on integration scope. With member and payment systems already in order, the work is mostly wiring up screens and goes quickly; multiple authentication methods or complex payment options extend it.
Q. Does an SDK affect app performance?
It affects size and startup. The practical checks are whether it only consumes resources when a broadcast screen is actually opened, and what it does in the background.
Related terms
Learn more
Last updated