The downside is that, being 30fps, your bitrate is heavily limited, thus your address space is limited, but this can be alleviated by geo-localization or combining IR beacons with BLE beacons, either by using BLE beacons to localize, or by synchronizing the BLE beacon broadcast with an IR pulse picked up on camera.
I would love to chat with you more. I'm a recent MIT alum and still in the Boston area.
How does your team try to combat the cost and the effort required by making this as economical as possible and also easy to use such that a person who is a beginner at technology such as using smart phones, computers, etc. can use it.
The moment real products will be in the marked that make use of the Reality Editor, you will power them up and just point your phone on them. It should not be more complicated.
Assuming we'll have rooms, buildings, and blocks absolutely packed with low-bandwidth radios like this; what radio standard is most promising at the moment?
I've seen some work out of Stanford (10.1109/VLSIC.2014.6858380) which looks interesting, but I'm not sure passive radios can harvest enough energy to do auth, which is a deal-breaker.
Apologies I haven't looked at the technical stuff yet (so may be an obvious question), but I was wondering:
Are the "API"s (what an object can be programmed to do) for the devices/objects (eg the switches) accessible locally?
As in is there enough embedded within the QR-like code to understand the API (or at least connect to the device, and it can "tell me more") or will it require cloud-based interaction?
Example case: if I'm in a room I've never been to before, no internet connection, and see a switch - would Instill be able to reprogram it then and there? Or do you see the (I)nternet of IOT as necessary?
The Reality Editor does not need to know a fixed API because the interface is basically a webpage that comes from the object it self. In that case you could say, the API is HTML5.
We have found a way to break down abstract standards in simple numbers: http://openhybrid.org/how-to-connect-everything.html
You can read here why it is so relevant: http://openhybrid.org/direct-mapping.html
And here you can read, why we will use more and more the physical world instead of the touch screen: http://openhybrid.org/learn%2c-setup%2c-operate.html
The Reality Editor is a digital screw driver. You only need it from time to time. Most of the time you will operate physical things around you.
Minor beef, however. The IoT will never take over if it isn't easy, easy, easy to use, and this has that in spades.
This is something we continuously work on with the open hybrid development tools.
On the other side, the marker is limiting the visual shape of an object. The limitation do provoke new shapes as well. It has some interesting properties.
Long story short. Technology is on its way and the marker will disappear. ;-)
There is so much more that we want to implement and some of it would give answers for your situation.
I think the Reality Editor will grow incremental and every version will be a bit better then the version before. In some years, when your car actually has this functionality, your scenario will be solved.
I had a talk at the last Solid Conference. Maybe that was the event you know me from?