|
|
|
|
|
by thetmkay
3839 days ago
|
|
Hi Valentin, great video! 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.