4 ms·
I am halfway convinced the idea of a "10 foot ui" driven by a remote is... well not wrong, but perhaps we could do better. Have the big screen be for just that,
by somat 1y ago
I am halfway convinced the idea of a "10 foot ui" driven by a remote is... well not wrong, but perhaps we could do better. Have the big screen be for just that, a spot to display video. Have the remote control, with the entire UI, be on a phone. I would keep the interface as a web interface so you don't have to screw around with an app to make it work, and include collaborative features so everyone gets to fight^wshare over what is shown.
- KetoManx64 1y agoYou can already do this with KDE-Connect. Touchpad input, send text, change volume, open URLs. Works great on my Media PC in the living room.
- ghc 1y agoI bet apple would actually be a great case study here. They have a great 10 foot UI, the world's shittiest TV remote, and a very easy to use system where your phone can be the entire UI and the TV can just play video (AirPlay). If people still use the 10 foot UI despite the bad remote, I think the 10 foot UI must be the right idea. Unfortunately I'm pretty sure apple will never share those usage stats with us.
- wolrah 1y agoThis is basically what a Chromecast was. Internally they were basically just an appliance that booted to a very minimal version of Chrome which could be remote controlled by a compatible application, web site, or device. It was a neat concept but I always found it annoying to have to keep going back to the app to control it when I was doing something else, or keep a tab open in my web browser, and it would often disconnect the session so no one could control it without just stopping and restarting entirely. You can still use that interaction model on the newer Chromecast-branded devices but they're also full-fat Android TV devices that can be used standalone with a dedicated remote control and run actual apps, which I think is a nice balance.