[valentin_heun]

Yes it would. The Marker (for visually identifying the object) and all interfaces are stored in the object it self. When you start the Reality Editor it finds automatically all objects in the same network.

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.

[cushychicken]

Hey Valentin. I love this concept. Do you have any notions to get rid of The Marker? I can see a lot of potential applications for this where the Marker would possibly interfere with a product's visual identity.

Minor beef, however. The IoT will never take over if it isn't easy, easy, easy to use, and this has that in spades.

[valentinheun]

Yes, this is a big thing. Our goal is it to make the creation of objects so easy that it can become a simple part of the workflow of a product + web designer. Very very very low entry barrier.

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. ;-)

[niutech]

Why did you choose HTML5 API and a heavy HTTP(S) protocol instead of more lightweight MQTT or CoAP? How about security?