recommended reading

To Turn the World Into a Web Page, Mobile Browsers Need to Improve Figuring Out Locations

Kostenko Maxim/

Augmented reality browsers use a mobile phone’s camera to digest a scene and annotate it with web-connected flair: live directions, geotagged tweets, reviews that hover over restaurants. But the current generation of AR browsers is lagging on geolocation, are content-poor, and have limited interactivity, according to a recent paper (paywall) in the Proceedings of the Institute of Electrical and Electronics Engineers (IEEE).

The researchers behind this paper, from Austria’s Graz University of Technology, argue that the AR browsers, which have existed since 2009, are not fulfilling their potential.

Geographic certitude is at the core of everything an AR browser does. Seamless AR browsing has to integrate sensor data from GPS (location); body direction (compass); and pose, or where the device is pointed (gyroscope and accelerometer). The Austrian team says that the current level of consumer-grade hardware can’t deliver all of this accurately, and that future AR browsers can overcome this by being more clever about the way they use computational resources.

For example, GPS sensors are prone to drift, which can throw off a browser’s ability to pinpoint location, so the Austrian team suggests instead relying on low-resolution GPS data to get the user’s approximate location, then using image-recognition software to fill in the details. They say the browser can build a panorama out of the physical view as the user sweeps the camera around, registering landmarks that each add to the browser’s certainty about where it should place content. Street-view data from Google could also help the AR browsers identify what they are looking at.

Beside the problems with geolocation, the authors called out the lack of compatibility between AR browsers, which they say has led to a dearth of decent AR content. When the Austrian team submitted their paper last summer, every AR browser was using its own proprietary framework for making content. It was as if Chrome, Safari, and Firefox all required web pages to be built using their individual language, instead of HTML. (For an example of what this would be like, try using Internet Explorer for a day.)

This might not be true for long. At last month’s Mobile Web Conference, the three most popular AR browsers announced an agreement to use a single language, called ARML 2.0 (Augmented Reality Markup Language). This framework was also accepted by the Open Geospatial Consortium, an international group that oversees standardization for location-based services. The language doesn’t specifically address how devices will use sensors, or how users of AR browsers will interact with objects on the screen, but it will open up the platforms to developers who can create shareable interactive-rich content.

The race is on to solve the problems with AR, especially now that Google has pulled back the veil on its own AR smartphone. Project Tango, still in prototype, doesn’t yet have a web browser. But, since Google is planning to ship 200 of these to developers, smart money would bet that the existing AR browser companies are scrambling to get their hands on a development model. A successful company could use Project Tango’s specialized cameras and hardware to push their browser’s scene-building, depth-sensing, map-making capabilities to the limit.

(Image via Kostenko Maxim/

Threatwatch Alert

Thousands of cyber attacks occur each day

See the latest threats


Close [ x ] More from Nextgov

Thank you for subscribing to newsletters from
We think these reports might interest you:

  • It’s Time for the Federal Government to Embrace Wireless and Mobility

    The United States has turned a corner on the adoption of mobile phones, tablets and other smart devices, outpacing traditional desktop and laptop sales by a wide margin. This issue brief discusses the state of wireless and mobility in federal government and outlines why now is the time to embrace these technologies in government.

  • Featured Content from RSA Conference: Dissed by NIST

    Learn more about the latest draft of the U.S. National Institute of Standards and Technology guidance document on authentication and lifecycle management.

  • A New Security Architecture for Federal Networks

    Federal government networks are under constant attack, and the number of those attacks is increasing. This issue brief discusses today's threats and a new model for the future.

  • Going Agile:Revolutionizing Federal Digital Services Delivery

    Here’s one indication that times have changed: Harriet Tubman is going to be the next face of the twenty dollar bill. Another sign of change? The way in which the federal government arrived at that decision.

  • Software-Defined Networking

    So many demands are being placed on federal information technology networks, which must handle vast amounts of data, accommodate voice and video, and cope with a multitude of highly connected devices while keeping government information secure from cyber threats. This issue brief discusses the state of SDN in the federal government and the path forward.

  • The New IP: Moving Government Agencies Toward the Network of The Future

    Federal IT managers are looking to modernize legacy network infrastructures that are taxed by growing demands from mobile devices, video, vast amounts of data, and more. This issue brief discusses the federal government network landscape, as well as market, financial force drivers for network modernization.


When you download a report, your information may be shared with the underwriters of that document.