Choosing Between iFrame and SDK
BlendVision provides two solutions for integrating streaming content into websites and applications:
1️⃣ iFrame Player – Quick and easy embedding
2️⃣ Player SDK – Full customization and control
To help you decide which fits your project best, let's explore their advantages and considerations.
Before You Start
For a foundational understanding of BlendVision's player solutions, check out:
🔗 What is an iFrame Player?
🔗 What is a Player SDK?
Key Considerations
iFrame Player
✅ Advantages:
- Quick and simple implementation for websites and applications (webview).
- Requires minimal development effort.
⚠️ Limitations:
- Limited control and customization within the container.
- May not seamlessly integrate with your website or application’s UI.
Player SDK
✅ Advantages:
- Full customization and advanced control over UI and playback.
- Provides a seamless, native experience across platforms.
⚠️ Limitations:
- Requires more development effort for integration.
- Supporting multiple platforms (e.g., Web, iOS, Android) increases workload.
Comparison Table
| Aspect | iFrame Player | Player SDK |
|---|---|---|
| Integration Effort | ✅ Quick and straightforward implementation ✅ Cross-platform compatibility for website and application (webview) | ⚠️ Requires API & library integration ⚠️ Different SDKs for each platform (Web, iOS, Android) |
| User Experience | ⚠️ May not integrate seamlessly ⚠️ Limited experience with all the components restricted within the container | ✅ Fully integrated experience ✅ No container limitations |
| UI Customization | ⚠️ Limited customization | ✅ Full customization capabilities which would not restricted by the container |
| Control | ⚠️ Limited control | ✅ Advanced control |
| Maintenance | ✅ BlendVision One handles updates | ⚠️ Requires developer effort for updates |