~/talk

Developing for Android TV and the Nexus Player

TalkinFrenchat DevFest Paris 2015 · on Friday, 2015-01-30· [android]
speakerdeck:ph0b
slides:none on file

How to adapt Android apps for Android TV and the Nexus Player: the Nexus Player uses Intel x86 hardware (64‑bit CPU) but ships a 32‑bit OS with only 1 GB RAM, which constrains memory use and native code choices. Android TV apps must declare a leanback activity, supply a non‑transparent TV banner, handle D‑pad focus navigation and overscan margins, and avoid assuming microphone/telephony/camera; native libraries should target x86/x86_64 or be packaged as per‑ABI APKs via Gradle, with emulators for testing and Play Console Android TV validation and uses‑feature checks for publication.

AI-written summary · about

  1. 0:00Android TV intro
  2. 1:27Android TV evolution
  3. 2:52Nexus Player specs
  4. 4:21TV controls
  5. 5:25UI tips for TV
  6. 6:49Play Store TV navigation
  7. 8:16TV design
  8. 11:08TV app dev
  9. 13:43TV manifest config
  10. 16:16TV interface best practices
  11. 18:47TV screen margins
  12. 20:54TV recommendations
  13. 22:17TV voice search
  14. 22:59Publish to Play Store TV
  15. 25:05TV permissions
  16. 27:12Manual TV validation
  17. 29:18Multiple APKs for TV
  18. 30:01x86 for TV
  19. 31:26Gradle multi-arch build
  20. 32:30Submit to Play Store TV
  21. 33:58Q&A
~/search
type to search 6,249 conferences, 138,987 speakers and 185,172 talks
~/help
cmdctrl k
search every conference, speaker and series
/
focus the filter search
h
home
c
conferences
s
speakers
e
series
t
light / dark — the status bar button does the same
?
this help
esc
close this, then clear every filter — or just the search, while you are typing in it

Ignored while you are typing. Pages without a filter rail have no search to focus.