Migration guide (Android SDK 2.0 -> Enigma River Android SDK)

Structural changes

While the flow of information throughout the SDK is still very similar (since both the old SDK and the new integrate towards the same Red Bee OTT backend) there are a few structural changes in the new SDK compared to the old one.

"Tech" is replaced by "PlayerImplementation"

The old SDK contains the concept of a Tech as an abstraction for a player technology. The new SDK contains a core-module that can work with any player technology. A player technology is now called a "player implementation". ExoPlayer is one player implementation. The player implementation used by an app has to be added separately as a dependency and injected into EnigmaPlayer.

Playback session

The new SDK introduces the PlaybackSession component which represents the playback of a stream beginning at the end of a successful play-call to the backend, and ending when the stream is stopped. This new component is essential and provides information about contract restrictions for the stream, tracks, and states of the stream (for example, live/not live).

---

Table of Contents
Introduction
• Structural changes (current)
Changes to SDK initialization
Changes to authentication/login
Changes to asset metadata retrieval
Changes to playback
Further reading