I've pondered a similar concept whenever I design an embedded system that needs a user interface. Provide a common formatted set of data (JSON say), a fallback interface (HTML,CSS,javascript), and an identifier for a better interface if the user's device can get to a network and snag an app or updated UI (URL).
Look at all the things around you in daily life with awful user interface devices, and yet you almost certainly carry a really nice UI device in your pocket and probably have a really great device in your bag.
Comments
I've pondered a similar concept whenever I design an embedded system that needs a user interface. Provide a common formatted set of data (JSON say), a fallback interface (HTML,CSS,javascript), and an identifier for a better interface if the user's device can get to a network and snag an app or updated UI (URL).
Look at all the things around you in daily life with awful user interface devices, and yet you almost certainly carry a really nice UI device in your pocket and probably have a really great device in your bag.
UPnP already does this. It can even include a presentation URL.