Last night at Google I/O a session was hosted about Android TV. Along with this new UI there was documentation posted about the new way apps can interface with it, using the
TvProvider APIs. This gives a lot of information about how this experience will work, as well as raising a few questions about how the experience will work.
Apps are using the Tv Input Framework
The APIs to add channels and programs may look pretty familiar.
Uri channelUri = context.getContentResolver().insert(
They actually are using the same APIs for Live Channels and the Tv Input Framework. To designate it as a channel to appear on the launcher, they are marked with
Looking at the new TvProvider support library, it does seem to have a number of similarities with the TIF Companion Library with the
Program classes. This support library also includes backported data columns and some more abstract classes. This is probably the future of the library.
There is also a channel logo each must provide. In staying with Google’s recent theme of circles for everything, these logos are masked into a circle.
JobService or any other way, these channels can be continually updated with new programs to keep users engaged. They are added similar to the programs in Live Channel’s TV guide, except these do not require static start and end times. They all appear as on-demand content which can be selected.
The first row is the app drawer and the second is your Watch Next. Every other channel is added underneath, in a seemingly chronological order. Apps must be in the foreground when they request to add new channels. Apps don’t have much control over where these new channels appear. There didn’t seem to be a way to move channels up and down, but that feature will likely appear.
This command opens up a dialog which requires user consent to add a channel, except for the first channel the app adds. Apps receive an intent when an app is first installed. This allows them to immediately add content to the homescreen for users.
This can also be controlled in settings. For example, YouTube will have three channels. Trending may be the only one shown at first, but two more are for your Recommended videos and 360-degree videos, which is coming to the new YouTube app.
Adding programs to the Watch Next list is pretty much the same as its own channel.
Uri watchNextProgramUri = context.getContentResolver()
The programs are just inserted, and can later be updated or removed. These programs can have a large number of properties.
WatchNextProgram.Builder builder = new WatchNextProgram.Builder();
Of note are the
WatchNextType, which shows the type of suggestion. This might be “Continue”, “New”, “Watch Next”, or “Watchlist”. There is also the
LastEngagement, which may be used for ordering the items in the queue. This time is simply the last time I watched the content.
How does this affect apps?
Reading through this guide, it makes me wonder how this will affect many apps, some of which I’ve written. Adding support for this feature isn’t hard, and this is one way to improve engagement between users and content.
It certainly moves away from the linear Live Channels system. Of course, live events and streams may still appear in the launcher, but it isn’t necessary. Apps like Cumulus TV may place each user-generated channel in its own “program” and everything is shown in a single row, with video previews.
Google will be working with third-party apps like Netflix, as well as their own apps like YouTube. So we will have numerous examples of how this feature should be implemented. Unlike the current launcher, this one is more opinionated. What do you think? Let us know in the comments below.