4 ms·

We explored ideas around this space at Emotely and Brass Monkey. There is much yet unexplored. This approach basically gets you a WiiU/Chromecast second screen

We explored ideas around this space at Emotely and Brass Monkey. There is much yet unexplored. This approach basically gets you a WiiU/Chromecast second screen platform: https://www.youtube.com/watch?v=NE8-TntjYB4 https://www.youtube.com/watch?v=NE8-TntjYB4 http://francoislaberge.com/blog/my-time-at-brass-monkey/ http://francoislaberge.com/blog/my-time-at-brass-monkey/

kannanvijayan 12y ago
This is sweet. I knew this was obvious enough of an idea that other people would have had it, and potentially taken it further. One of my longer-term thoughts on this approach is that it may extend beyond simply a "controller" notion. Ultimately, I was thinking the phone could become the sole state carrier, and all other devices (workstations, laptops, game consoles, projectors) could become stateless endpoints which are ephemerally controlled as needed. For example, you could arrive at home, connect your phone to your home computer, and initiate a "home session" which kicks off all the 'webapps' you have defined for your home-computer environment, on your home computer. The apps are structured client/server, and they save their state back to the phone (but use the computer's processing, display, audio, etc.). When you're done, you disconnect and leave. All your state is saved to your phone, and any other computer you come across can temporarily become your "home computer". Likewise, any computer can be your "work computer". And any game console can be "your" game console. The phone, in this context, seems like the ultimate proxy for the individual. It travels with a person. It has access to the inputs and data in the vincinity of the individual. It can be controlled by the individual. What better place to put all of your computational state, than in there? Anyway, this was some far-fetched, pie-in-the-sky thinking I had about the long-term implications of such an architecture. Happy to see other people working on the concept.
- endergen 12y ago
  I agree. We focused on the controller use case as it made for a simpler API, but it was always my interest to make it more generalized. Just perhaps through a different product that was more open and generalized. Things like having your phone cache webapps that could be casted over LAN (thus not requiring a persistent connection), this would useful for playing say games/apps when on planes or log cabins, etc. Or having the phone create metascreen, synchronizing multiple monitors with fullscreen webpages open that you would split up the graphics of a game or movie to run across all the screens, thus making a bigger screen. So many possibilities. Ultimately though, I'm still on the fence to if this is the best approach vs a mixed approach of using bluetooth, zigbee, wifi, http, websockets, normal sockets, and etc all abstracted to use whatever each device has to offer.
- endergen 12y ago
  Great write up too, by the way.

kannanvijayan 12y ago

This is sweet. I knew this was obvious enough of an idea that other people would have had it, and potentially taken it further. One of my longer-term thoughts on this approach is that it may extend beyond simply a "controller" notion. Ultimately, I was thinking the phone could become the sole state carrier, and all other devices (workstations, laptops, game consoles, projectors) could become stateless endpoints which are ephemerally controlled as needed. For example, you could arrive at home, connect your phone to your home computer, and initiate a "home session" which kicks off all the 'webapps' you have defined for your home-computer environment, on your home computer. The apps are structured client/server, and they save their state back to the phone (but use the computer's processing, display, audio, etc.). When you're done, you disconnect and leave. All your state is saved to your phone, and any other computer you come across can temporarily become your "home computer". Likewise, any computer can be your "work computer". And any game console can be "your" game console. The phone, in this context, seems like the ultimate proxy for the individual. It travels with a person. It has access to the inputs and data in the vincinity of the individual. It can be controlled by the individual. What better place to put all of your computational state, than in there? Anyway, this was some far-fetched, pie-in-the-sky thinking I had about the long-term implications of such an architecture. Happy to see other people working on the concept.

endergen 12y ago
I agree. We focused on the controller use case as it made for a simpler API, but it was always my interest to make it more generalized. Just perhaps through a different product that was more open and generalized. Things like having your phone cache webapps that could be casted over LAN (thus not requiring a persistent connection), this would useful for playing say games/apps when on planes or log cabins, etc. Or having the phone create metascreen, synchronizing multiple monitors with fullscreen webpages open that you would split up the graphics of a game or movie to run across all the screens, thus making a bigger screen. So many possibilities. Ultimately though, I'm still on the fence to if this is the best approach vs a mixed approach of using bluetooth, zigbee, wifi, http, websockets, normal sockets, and etc all abstracted to use whatever each device has to offer.
endergen 12y ago
Great write up too, by the way.