Android Is Not Just Mobile: Lessons from TV, Auto, and Wear
Abstract
Most developers see Android through the lens of smartphones, while Android TV, Auto and Wear OS require a different mindset rather than an adaptation of the same one. This paper shares architectural lessons and UX challenges from building applications for those non-mobile platforms, where the input model, the viewing distance, the lifecycle and the constraints on memory and power all differ from the phone case that most Android practice is built around. Based on a presentation given at GDG Berlin, it sets out how to extend Android skills beyond the phone screen without assuming that what works there transfers. Readers take away a clear understanding of the architectural and lifecycle differences between mobile and non-mobile Android platforms, together with practical strategies for layout optimization and memory management specific to those ecosystems, where the same mistake that is tolerable on a handset is not on a television or a watch.
- Published in
- Proceedings of the Raptors Conference, Vol. 1 (2026)
- Conference
- Raptors Conference 2026, 21 October 2026, online
- Accepted
- 2026-09-20
- DOI
- https://doi.org/10.68495/rc.2026.C083
- Presentation
- Slides (PDF)
- Licence
- © 2026Siarhei Krupenich. Published under Creative Commons Attribution 4.0 International (CC BY 4.0).
- Publisher
- Hackathon Raptors, Community Interest Company 15557917, London, United Kingdom
- Permanent address
- https://proceedings.raptors.dev/krupenich-android-is-not-just
Open access. Every entry in the Proceedings is free to read, with no charge to authors and no charge to readers. Slides are served from this site, so they stay available at the paper's permanent address.
Cite this paper
Siarhei Krupenich (2026). Android Is Not Just Mobile: Lessons from TV, Auto, and Wear. Proceedings of the Raptors Conference, Vol. 1 (2026). Hackathon Raptors, London. https://doi.org/10.68495/rc.2026.C083
@inproceedings{raptors2026-c083,
title = {{Android Is Not Just Mobile: Lessons from TV, Auto, and Wear}},
author = {Krupenich, Siarhei},
booktitle = {Proceedings of the Raptors Conference},
volume = {1},
year = {2026},
publisher = {Hackathon Raptors},
address = {London, United Kingdom},
doi = {10.68495/rc.2026.C083},
url = {https://doi.org/10.68495/rc.2026.C083},
abstract = {Most developers see Android through the lens of smartphones, while Android TV, Auto and Wear OS require a different mindset rather than an adaptation of the same one. This paper shares architectural lessons and UX challenges from building applications for those non-mobile platforms, where the input model, the viewing distance, the lifecycle and the constraints on memory and power all differ from the phone case that most Android practice is built around. Based on a presentation given at GDG Berlin, it sets out how to extend Android skills beyond the phone screen without assuming that what works there transfers. Readers take away a clear understanding of the architectural and lifecycle differences between mobile and non-mobile Android platforms, together with practical strategies for layout optimization and memory management specific to those ecosystems, where the same mistake that is tolerable on a handset is not on a television or a watch.}
}
TY - CONF TI - Android Is Not Just Mobile: Lessons from TV, Auto, and Wear AU - Krupenich, Siarhei T2 - Proceedings of the Raptors Conference VL - 1 PY - 2026 DA - 2026/09/20 PB - Hackathon Raptors CY - London, United Kingdom DO - 10.68495/rc.2026.C083 UR - https://doi.org/10.68495/rc.2026.C083 AB - Most developers see Android through the lens of smartphones, while Android TV, Auto and Wear OS require a different mindset rather than an adaptation of the same one. This paper shares architectural lessons and UX challenges from building applications for those non-mobile platforms, where the input model, the viewing distance, the lifecycle and the constraints on memory and power all differ from the phone case that most Android practice is built around. Based on a presentation given at GDG Berlin, it sets out how to extend Android skills beyond the phone screen without assuming that what works there transfers. Readers take away a clear understanding of the architectural and lifecycle differences between mobile and non-mobile Android platforms, together with practical strategies for layout optimization and memory management specific to those ecosystems, where the same mistake that is tolerable on a handset is not on a television or a watch. LA - en ER -