The Conviva SDK 4.x version is significantly simplified when compared to the Conviva SDK 2.x version. It reduces integration time and effort, and enables solid foundation for future Conviva sensor implementation. Conviva strongly recommends migrating to Conviva SDK 4.x version. Only the Conviva SDK 4.x version will have new features implemented going forward.
The below table describes the benefits of migrating to Conviva SDK 4.x version.
| Benefits | Category | Description |
|---|---|---|
| Stateless Integration | New Feature | Event-driven stateless integration instead of session management. |
| Faster / Simpler Error Reporting | New Feature | No need for player state manager or session cleanup. This has reduced error-reporting to one API call. |
| Ad Break Reporting | New Feature | SDK takes care of sending custom events, pausing VST during pre-rolls, and detaching player. This has reduced ad break handling to one API call. |
| Coding Style Improvements | Cost of Ownership | Cost of owning the platform decreases as less development work is needed to maintain successful integration.
|
| Developer-friendly Syntax | Cost of Ownership | Streamline workflows with intuitive API naming and improved code readability.
|
| App-level Events | New Feature | Simpler handling of use cases. For example, backgrounding:
|
| Ad Integration in Synchronization with Ad-manager Events | New Feature | Ad sessions are no longer managed like video content for Ad Insights.
|
| Metadata (Platform) | New Feature | Virtual interface implementation is no longer required to retrieve device specific metadata. |
| Features | New Feature |
|