Week 3 Summary: Argon
In this paper, the authors introduce how they design the Argon AR Web Browser and what there application environment is like.
First of all, the requirement of success is defined: All AR content is presented in one unified AR application environment. And a lot of so-called AR Browsers are criticized because they fail to think about whether the proposed architecture could be deployed in a practical way. Besides, these AR Browsers cannot help designers have a high degree of control over the look, feel and interaction of their content.
Mobile Phone are chosen as the development platform because it is ubiquity. The development of mobile computing supports the techniques of mobile AR. And mobile WWW architecture will also be mature enough to be the application environment. In this case, researchers determine to realize three goals: to create an AR application environment, to build on existing mobile technology as much as possible and to create an ecosystem that supports easy and sophisticated authoring of applications. Finally their project contributes to demonstration that the web is a viable mobile AR platform, the KARML specification, the Argon multi-channel AR architecture and demonstration that the web-centric approach is powerful.
In the next sections, three main architectural components are discussed in details, that is, how Argon integrates with the web, the internal architecture of Argon, and the KARML markup language. A lot of illustration examples are provided to help readers understand their work. In the future, some new features, such as 3D model rendering, support for other markup languages, natural feature tracking, and so on, will be added in Argon to improve its ability to create AR application.
My Question to the authors is: How to balance the space occupation between virtual information and reality on the web? Sometimes we don’t have much room for virtual info. But if we don’t give it enough space, font size and image size will be a big problem. Zooming in and out may be an appropriate solution, but it will lead to more steps for users to check the information. How to do the trade off here?
Comments are closed.