Frequency is accessible via SDKs for iOS and Android, or REST APIs in any environment.
Developers can choose how to integrate with Frequency. There are two basic integration approaches, and resulting architectures, although developers are free to choose a hybrid approach of their own.
Client applications will typically access the Frequency services using the SDKs. These present a convenient set of interfaces and helper functions. Developers are shielded from low-level communication and having to manage JSON objects.
Clients are, however, free to access all Frequency services using the REST APIs should they wish.
Server-side integration is invariably performed using the REST APIs, although a subset of functions is available for Java environments using the Android SDK.
Client Side Integration
Client applications can perform all functions directly via the SDK, including calling content discovery services, retrieving “Your Highlights” feeds for users, continuously playing collections of videos, etc. Frequency’s own mobile applications use this model.
Managing a wide variety of media sources is one of the more difficult parts of developing an internet video app. The Frequency Player, included as part of each SDK, simplifies this by encapsulating and abstracting all needed video playback mechanisms. Developers can simply send generic play instructions to the Player, and it takes care of the rest.
The Player manages all aspects of playback. It manages bandwidth across all different connection types, is location aware and handles geo-restrictions. It can be used chromelessly and normalizes player controls across all media. It performs device detection, error handling, format selection, continuous play even in full screen mode, and dynamically loads third party players, transparently, when needed.
The Frequency Player can be mixed and matched with the iOS and Android SDKs, or used directly with the Frequency REST API.
Server Side Integration
Developers perform server-side integration to integrate Frequency into existing business and operational support systems (B/OSS). This often includes content management systems (CMS), authentication services, EPGs, and other back-end and head-end systems.
Deployment of Frequency’s service in environments that include thin clients or older set-top-boxes, will typically require some server-side integration.
Server side calls are made to retrieve lists of content categories, curated and algorithmically-generated channels, metadata for videos and collections of videos, search, etc. Server side calls can also be used for user profile management functions such as creating accounts, attaching and authenticating social accounts, etc.
Visit the Developer Resources section to get started. Everything you need to integrate Frequency services into your applications and platforms can be found here, including complete documentation, and sample apps and source code.