The Android SDK is significantly more performant than the Legacy Android SDKs (4.12.x), as it removes the dependency on the WebView to handle video-playback and supported features. Removing the WebView dependency also allowed to move many of the APIs from being asynchronous to being synchronous, such as querying the current time.
Another difference between the SDKs is that with Android SDK users will no longer need to maintain multiple flavors for different platforms or Android OS version. This because the Android SDK works on Android mobile, Android TV and Fire TV devices with Android OS version 5.0+ (API level 21 and above).
The Android SDK moves towards more modularized features, which means there is a base SDK that can handle basic playback and additional feature integrations are provided as separate modules that can be added as desired. This approach gives more flexibility and results in a reduced application size, since non-required parts are not included in the build of the application. You can read more about this here.
The Android SDK leverages Java 8 and Kotlin languages to provide safer and more concise code.
Lastly, the Android SDK is released on JitPack which allow developers to easily fetch and implement the player into their app.
THEOplayer Android SDK 5.0 is a more performant version of our SDK, so we advise you to migrate as soon as possible.
However, the 5.0 SDK is built from the ground up so from day 1 it will be not in feature parity with the legacy SDKs.
What features are covered already in THEOplayer Android SDK 5.0?
If the implemented features are covering your use-cases, feel free to upgrade. The changes due to deprecations in your code will be minimal, THEOplayer Android SDK 5.0 tries to be backward compatible with the legacy 4.x APIs as much as possible.
If your use-cases rely on missing features and you can not implement them on top of the player.
Some features, like:
Or features which brought to life via the WebView's middle layer:
Or you rely on the default THEOplayer UI.
The current THEOplayer Android SDK 5.0 is chromeless, it means you need to implement your own native UI on top of the player.
Soon we will also release a fully native, customizable UI module (connector). Stay tuned!
There are 2 main things you need to consider during migration:
For these ones please consult with our changelog
You can read more about the new architecture here.
To migrate each modularized feature, please visit our Features subpage.
After these steps you should be able to compile your project and benefit from THEOplayer Android SDK 5.0.
The Google Cast and Google IMA/DAI integration APIs are mapped to
theoplayer.cast.chromecast APIs, but you can also access the same APIs (and new ones) on the integrations itself.