Christian Kurzke discussed why developing for TV is an opportunity given the rise of internet-connected TVs, considerations for designing user interfaces optimized for 10-foot viewing, and steps for getting apps to market including ensuring they are compatible with Google TV and do not require touchscreen input. He provided tips for UI design, monetization strategies, and resources for developers building apps for the television platform.
4. Why Develop for TV?
• In the US, homes have an average of 2.5
people and 2.86 TV sets (and rising!)
Television Audience Report, 2009: The Nielsen Company
• In the US, people “watch” an average of
~5 hours of TV per day
Three Screen Report, Q1’10: The Nielsen Company
5. Why Develop for TV?
• 22% of US broadband households already
own an HDTV with integrated TV apps
Source: In-Stat, "Q2'11 US Digital Entertainment Database," July 26, 2011
• 60% of connected-TV households will use a
TV app at least once per week
Source: In-Stat, "Q2'11 US Digital Entertainment Database," July 26, 2011
• By 2015, 500 million web enabled TVs
Source: Crave Asia, July 8, 2011
6. The Opportunity
• Be the center of every family room
• Enhance peoples TV watching (5 hr/day)
• Create the new “killer app” for the
“other” 19 hr/day
9. Significantly improved version 2
Introduction to Google TV
Better, simpler UI Google Play for TV-optimized apps
All applications Chrome Browser for full internet access
Google Confidential and Proprietary 9
13. Creating Android Apps
Not “just” a big screen
Android Device:
• UX adapted to 10ft
• Input Device (no Touch Screen)
• Many Optimized Media Codecs, DRM, HLS,
etc.
14. Developing for Google TV
• Everything you love about Android:
• Deep Integration with System
• Familiar Language
• Powerful APIs (Media Players,
Renderscript, OpenGL)
• ... And MORE!
20. Remember what we said
about Memory!
MB / fullsize screen image
QVGA HVGA WVGA WXGA 1080p
0.3MB 0.5MB 1.5MB 4MB 8MB
21. UI Design Tips
• Not “just” a big screen Android
• Focus on vital parts of your application
- Group content, controls & interactions by priority
(use progressive disclosure)
• Throw out the non-essential (keep it simple)
• Multiple screens better than overloading users
• Design using fluid layout and scalable assets
(9-patch images)
• Have a simple mental model
• Consider hiring an interaction designer
21
25. Available Features
• com.google.android.tv
• android.hardware.location
• android.hardware.location.network
• android.hardware.usb.host
• android.hardware.wifi
• android.software.live_wallpaper
26. The “Key Feature” for Google TV
Main difference between TV and other Android devices:
The TV is across the living room “10 ft” away:
NO TOUCH SCREEN
Android market only displays apps which explicitly do
NOT require “touchscreen” feature.
<uses-feature
android:name="android.hardware.touchscreen"
android:required="false" />
27. One App for All Android
<uses-feature
Text
android:name="android.hardware.touchscreen"
android:required= “false” />
Check at runtime if it's a Google TV:
getPackageManager().
hasSystemFeature("com.google.android.tv");
Google TV Only:
<uses-feature
android:name="com.google.android.tv"
android:required= “true” />
28. Verify your APK
Use the “AAPT” tool to verify all your Manifest tags.
Will display Features, Permissions, etc. “as seen” by Market!
Text
#> aapt dump badging MyApplication.apk
package: name='com.mydomain.greatapp'
targetSdkVersion:'12'
uses-feature-not-required:'android.hardware.touchscreen'
uses-feature:'com.google.android.tv'
uses-permission:'android.permission.INTERNET'
uses-permission:'android.permission.ACCESS_WIFI_STATE'
uses-feature:'android.hardware.wifi'
29. Pricing / Free vs. Paid
•Free Paid
• Users like free - there • Price it right, relative to your
are significantly more category
impressions and • Test price sensitivity and
installations of free vs. elasticity
paid apps
• Free with ads Freemium
• Affiliate models • Freemium model is very
popular in Market
• Extension of existing service
• In-app billing
• “License” APKs
29
30. Development Devices
Tablet with (Bluetooth) Keyboard
•Test Navigation, Focus, etc.
Emulator (for Linux workstations)
•Test Screen Sizes, Overscan, etc.
Get the real device
• Sony, Logitech Revue and more... :)
32. Getting a Logitech Device
• Goto URL: http://goo.gl/GkZqm
• Use Referral Code:
CGK-DROIDCON-2012
33. We’re Here to HELP!
http://developers.google.com/tv/
Twitter
@GoogleTVdev
Find us on:
stackoverflow.com
Tag: Google-TV
Google Groups:
googletv-android@googlegroups.com
Google +:
Weekly Hangout