Posts

An AR Case Study – NS804’s First AR Venture

Takeaways From NS804’s First AR Venture – An AR Case Study

Augmented reality (AR), is still being mastered by tech and software professionals alike. While there have been bounds and leaps made in the pursuit of developing more complex and more robust AR technology. These advances support the delivery of more immersive, realistic, and functional AR applications. NS804’s introduction to building an AR application came a few years ago and was mostly accomplished using the antiquated AR Kit 2. While there have been major advances in the software available to building AR, a lot of the core-concepts NS804 learned through this build apply, and will continue to apply to all AR applications now and in the future. This AR case study will evaluate and address some of the issues and complications that arose through the duration of this AR project. Then, the AR case study will detail some of the main lessons and takeaways from the project.

The Ask

The client in this instance was asking for an AR application that would relay data from machinery and equipment to a collector, without the need for the collector to ever come within eyesight of physical contact of the machine from which they’re pulling data. This data refers to the ‘vitals’ of the machinery and included aspects like temperature, pressure, load capacity, and other integral information regarding the machines maintenance and operational efficiency. This was a complicated project because it involved using coordinates and GPS navigation to pinpoint the equipment location, and feed that information into the AR apps map.

The Obstacles

In approaching this complication there were multiple hurdles that needed to be addressed. Firstly, there was an issue with accuracy. As even the most powerful satellite mapping can only provide an accuracy of five meters, give or take, pinpointing the exact location of the machinery became difficult. What added to this difficulty was the equipments proximity to itself. Oftentimes, different machines would be less than 100 yards away from one another. This accentuates the accuracy issue, providing another obstacle NS804 needed to work around.

In addition to the accuracy being an issue for the machines themselves and their placement on the AR interface, the tags that were required to populate also ran into a proximity issue. The tags would populate overlaying one another, or start to flicker instead of hold solid when appearing in AR.

Another complication occurred in building the perspective of the AR interface. Since there is a specific aspect to positioning in AR, and since AR was still brand new at the time; there was a lot of learning and trial by error conducted. Luckily for you, NS804 has done the work of pioneering, so they’re in a position to help design, consult, and guide on the most sophisticated and robust AR apps on the market.

Solutions

The solutions for the main obstacles above were all integrated and related. The first aspect of the comprehensive solution to these problems revolving around positioning and placement had to do with orientation. In AR, everything has to be oriented to true north – it’s how the position of virtually everything is calculated. This anchors the AR interface which was the first step to solving these issues.

Once the app was oriented toward true north, the next step was creating a more user-friendly perspective. In the first iterations, the perspective was delivered through a sort of cone-view. This was disorienting and hard to use. Instead, the app was designed to place the user in the middle of area they were surveying. This allowed the user to then use the AR app as a sort of lens, and as they moved it along their survey-area, different tags would populate.

This leads to the next issue that NS804 needed to address in order to deliver a functional, and user-friendly experience to the client. As the user viewed their survey area, and information tags began to populate; the info-tags would begin to flicker in and out. It was soon discovered that these info-tags would flicker if they were set to the same depth. Setting the tags to varying depths solved this issue, making it possible to keep the tags from overlapping and flickering in and out.

All-in-all the bulk of the complications that arose during this build were involved with the visual aspect and perspective in one way or another. NS804 was able to successfully deliver the client-ready version in about 60 days and after around 25 iterations. Being at the onset of the AR-era, NS804 could build an app of similar capability today in 2-3 weeks and more than half the iterations. This is massive jump in efficiency stems from more advanced and more robust AR design software available, as well as the experience involved in building this AR app and learning a lot of the core theories of AR design.

Key Takeaways From the AR Case Study

This AR case study should highlight a variety of important lessons regarding the development of AR applications, the trial-and-error process, and knowledge that comes with experiencing an AR design and build firsthand.

True North: In designing an AR application NS804’s first big-lesson was in orientation. Orienting everything that renders within the AR universe to true-north is how the entirety of an AR application locates everything. This enables other functionality of the AR like mapping, and positional population – as was necessary in this design.

Centered Perspective: This was another positional setting that NS804 learned in regards to creating AR applications. Centering the user perspective within the AR universe allows an expanded and more user-friendly visual field. Rather than viewing the world through a distorted “cone-view”, centering the user allows for a more comfortable user experience, plus it’s less straining on the eyes.

Layering: The third lesson related to positioning and orientation, as well as the visual experience – had to do with layering the environment successfully. This involved placing information-tags that carried the sought-after data at different depths within the AR environment. This eliminated the issues that were posed by overlapping tags that had a bad habit of flickering.

Prepared to Pivot: The final takeaway from this client project was be flexible and capable of pivots. After the successful delivery of this build; the client immediately began discovering additional uses for the software that would require additional builds and versions. These future visions revolved around converting the AR application into a marketing and sales tool. While these iterations have yet to be realized, the ability to adapt, evolve, and improve should always be the foremost priority of software developers and mobile app designers.

This AR case study illuminated a lot of knowledge into AR design for NS804, and it’s our hope that it acts as a good guide for other industry professionals looking for documentation on developing an AR application.

A similar project undertaken by NS804, today, could be accomplished in a fraction of the time. Rather than a two-month turnaround with over 25 reiterations, and a prolonged testing period, NS804 could deliver the same level of an AR application in a 2-week-timeframe. This is capable today because of learned knowledge from the original project, an upgrade in AR building software available, and more accessible and comprehensive information regarding AR that is also available.

NS804 is dedicated to making mobile app development services of any scale, available to anybody. Armed with years of experience across industries, softwares, and platforms NS804 is an excellent choice for appreneurs looking for assistance designing their next mobile-app venture. Get in touch with NS804 today to start the design-discussion, and receive expert-level guidance on your mobile-app venture.