ARkit versus Vuforia

With the release of ARki 2.0 we made a challenging decision to re-develop the app with the inclusion of a marker-less AR solution, ARkit, versus our previous marker-driven SDK provided by Vuforia. The pro and cons of both solutions were extensive, and we deliberated over this decision tirelessly. However in the end ARkit won, and today I wanted to go over some of our reasons for why we chose to upgrade to ARkit over our beloved Vuforia SDK. 

Advantages of ARkit SDK

1.) Marker-less AR
The most impressive feature about ARkit is just how clever it is about picking up the environment around you using “world tracking” capabilities. By integrating a technique called visual-inertial odometry, ARkit uses the camera and motion sensors within an iOS device to track the environment, and overlay virtual data with a high degree of accuracy. The use of Marker-less AR means that ARki is able to be deployed in any environment, without the need for printed images or placeholders. The use of ARkit allows the app to detect horizontal planes, such as tables, and floors, and superimpose 3d models directly on top of the camera feed. This important feature means that architectural models are no longer bound to the confines of paper space and can now be viewed at 1:1 scale, on-site! Spatially this capability also allows users to explore virtual models in walk-through format, easily navigating through digital spaces like a virtual AR game-scene.

2.) Light Estimation
An interesting feature of ARkit SDK means that the lighting for 3d models can be realistically updated in real-time based on the light available in the environment. ARkit uses the camera sensor to estimate the total amount of light available and applies the correct lighting to virtual objects.
​ 

Disadvantages of ARkit SDK

• limited to only the latest iOS devices 

ARKit runs on the Apple A9, A10, and A11 processors, which means that all mobile devices prior to iPhone 6s and ipad (2017) are excluded from enjoying a marker-less AR experience.  Below are the iOS devices that will be able to run ARKit apps:

1. iPhone 6s 
2. iPhone 7 
3. iPhone SE 
4. iPhone 8 
5. iPhone X
6. iPad Pro 
7. iPad (2017)

• Virtual Models cannot be calibrated prior to launch. 

The main disadvantage of not using a 2d printed/ 3d marker to drive AR is that the virtual scene will need to be re-calibrated every time the app is launched. This means that the user is fully in charge of setting up the AR scene based on his/her environment, and available plane detection. Although the Marker-less experience frees up a lot of limitations based on model size and spatial exploration, the ability to mark certain locations/artefacts with a pre-compiled virtual scene is not really possible unless a marker is included with the AR experience. 

​Advantages of Vuforia SDK

• Not limited to iOS devices 

The key advantage of Vuforia is that it can be used for iOS, Windows and Android devices. Moreover, the SDK is easily integrated for older devices and not limited to the latest processors as defined by ARkit sdk. 

• 3d Tracking 

The use of 2d marker driven AR is nothing new within the Augmented Reality world, however the integration of 3d tracking capabilities incorporated within the Vuforia SDK means that standard physical objects, such as 3d prints and physical architectural models, can be used within the app as markers, which can be superimposed with virtual data. This allows for additional levels of interactivity to existing physical models in ways that could enrich the user experience beyond measure. 
​

Disadvantage of Vuforia SDK 

• License Fees 
  

One of the main drawback of incorporating Vuforia SDK is that it cost $499 for license fees per app. 

•  Requires a printed Marker to work. 
  

The disadvantage of requiring a printed Marker to kickstart the augmentation is that you are always confined to the use of a printed image to view models in AR. Although Marker recognition for 3d tracking has several benefits, the use of 2d images for augmentation can become slightly restrictive when you need to present the model/ app remotely, or in an outside setting. The printed marker also limits the size of the AR visualisation to the confines of paper size, and therefore prevents from having seamless walkthrough demonstrations without large-scale industrial printouts.  

Conclusion: 
Overall our investigations into AR SDK’s have given us many hours of exploration into the best possible route for ARki. We continue to stay open with the specific development tool we choose to work with, because the options are so varied, and very dependent on the requirements of the project in question. In reading this post I hope that the differences between ARkit and Vuforia has become more clear, and that the one you choose can essentially lead you to the most exciting AR experience yet.