Mirage, AR, and how the future will be augmented (Part 1 of ???)
The Idea.
To
understand our project I thought it would be best to first understand our
vision, and who we are. We liken ourselves to Google, Elon Musk, and Gabe
Newell. We believe that if we innovate, if we avoid doing the mundane, if go
big, and never go home that not only can we create a startup. We hope that we
can make something that changes the way the world works. Difficult yes, time
consuming yes, foolish yes, but the hope is that wake every morning an hour
before ever other startup founder, and go to bed an hour later then maybe we
can make this work.
Mirage is augmented reality for the masses. The same way the web, JavaScript, html, and Google change the web. We hope to reenact in the augmented reality web with mirage dns, ARscript, ARhtml, and the Mirage mobile browser. The idea is that if we can build infrastructure, and give enough room for people to actually do something with then we can make a living and the same time make a difference. The basic idea is both simple yet big, give people a way to take any object, scan it, and then give it information that can display right onto that object. This is the same way the web works though text links. To make this a possibility you need the same things the web has.
First you would need a way to view links. This is proposed augmented reality browser for Android, and soon for the iPhone. With the ability to use and view the links we will do custom development. This can be stored and access from the device.
Second you would need coding practices. We hope to bypass this as first with an easy to use blogger/Wordpress interactive AR building environment. We made a simple and easy to use augmented reality building web app. Then the idea is to in a years’ time hopefully create a scripting language and markup specific for augmented reality. The markup itself is already being used in Mirage to make the creation of popups simple though we need to create some standardization.
Lastly you need the big infrastructure. Basically this would be servers that can host an AR API, and a DNS which can turn images in digital links. The server is something that can be developed using any server, so no much thought has gone into changing that concept. A DNS though or a central database that would allow ever AR app to apply information onto an item is something we are actively working on. In the next 6 months we hope to have both a server and an open source DNS working for the public.
This will be the first of many blogs by me and the team. We want to document the process. I just guessed if any you're looking to change the way the world work you might as well documented it.
Mirage is augmented reality for the masses. The same way the web, JavaScript, html, and Google change the web. We hope to reenact in the augmented reality web with mirage dns, ARscript, ARhtml, and the Mirage mobile browser. The idea is that if we can build infrastructure, and give enough room for people to actually do something with then we can make a living and the same time make a difference. The basic idea is both simple yet big, give people a way to take any object, scan it, and then give it information that can display right onto that object. This is the same way the web works though text links. To make this a possibility you need the same things the web has.
First you would need a way to view links. This is proposed augmented reality browser for Android, and soon for the iPhone. With the ability to use and view the links we will do custom development. This can be stored and access from the device.
Second you would need coding practices. We hope to bypass this as first with an easy to use blogger/Wordpress interactive AR building environment. We made a simple and easy to use augmented reality building web app. Then the idea is to in a years’ time hopefully create a scripting language and markup specific for augmented reality. The markup itself is already being used in Mirage to make the creation of popups simple though we need to create some standardization.
Lastly you need the big infrastructure. Basically this would be servers that can host an AR API, and a DNS which can turn images in digital links. The server is something that can be developed using any server, so no much thought has gone into changing that concept. A DNS though or a central database that would allow ever AR app to apply information onto an item is something we are actively working on. In the next 6 months we hope to have both a server and an open source DNS working for the public.
This will be the first of many blogs by me and the team. We want to document the process. I just guessed if any you're looking to change the way the world work you might as well documented it.
No comments:
Post a Comment