VuMarks are the next-generation bar code. They allows the freedom for a customized and brand-conscious design while simultaneously encoding data and acting as a trackable AR target. VuMark designs are completely customizable, so you can have a unique VuMark for every unique object.
The VuMark provides a universal solution for delivering unique AR experiences on any object, while allowing the design freedom for a custom look and feel that is retained across any number of targets. VuMarks provide a simple method for encoding data such as a URL or a product serial number that overcomes the limitations of existing matrix bar code solutions that do not support AR experiences and also detract a product’s appearance. The same VuMark visual design can be used to encode a range of unique IDs or data into one image, icon, or logo which is useful for presenting a common identifier across a product range.
Summarized, the trademarks of a VuMark is the ability to
- present millions of uniquely identifiable instances.
- encode a variety of data formats.
- differentiate among identical looking products based on their Instance ID.
- Track VuMarks continuously in 3D
VuMarks are a game changer for the enterprise because they offer a scalable way to identify objects and overlay 3D step-by-step instructions in pertained areas that could improve maintenance or training sessions. This leads to significant cost savings for employees operating and servicing equipment.
In the consumer market, VuMarks offer a reliable way to recognize and track toys, electronics, and tools. Consumer brands can create 3D experiences that are designed to show how to use the product or to add value with new digital features.
Try out VuMarks with the Unity Core Sample which is available here.
VuMarks are created in the Vuforia Target Manager using Scalable Vector Graphics (SVG) files as input. They can be added to a VuMark database that you configure online and then download from the Target Manager. The database can be added to your Vuforia Engine project in Unity, Android Studio, XCode or Visual Studio and packaged with your app's executable.
VuMarks are printed targets and can be placed on any planar surface or imprinted on an object in a discreet size. They are further subject to the same requirements as to that of other printed Vuforia Targets and glossiness, reflections and lighting settings can all affect its tracking capabilities. See Physical Properties of Image Targets for more information.
The following table summarizes the dependencies between the VuMark feature and the Vuforia Engine license type
Vuforia Engine License Type
VuMark Target Manager Capabilities
VuMark SDK Capabilities
|Development, Classic & Cloud||
||Load and activate one (1) VuMark database per app|
|Pro & Enterprise||
||Load and activate more than one (1) VuMark database per app|
For additional details about the capabilities of each Vuforia Engine license type, please refer to our pricing page.
NOTE: That one of the behaviors of attempting to load and activate more than one (1) VuMark database using a Development, Classic or Cloud license is that only one database will be enabled. The database enabled depends upon the order in which they are activated.
Creating and Managing VuMarks
VuMark designs can be created in Adobe Illustrator using the Vuforia VuMark Designer plugin. There are a few basic rules for designing VuMarks that are explained in detail in the VuMark Design Guide. In general, VuMarks have five primary design components that contribute to their uniqueness, detectability, and data encoding capabilities.
The first step is therefore to work on the design of the VuMark and determine the type and number of instances it will generate. Follow our guide on Designing a VuMark in Adobe Illustrator to generate a VuMark with your own design.
Once a VuMark is created as an SVG file, it can be uploaded to the Vuforia Target Manager as a VuMark template to an already created VuMark Database. When the VuMark template is uploaded and verified, an instance can be generated from the VuMark template that has encoded unique identifiers, strings, numbers or bytes. To learn more on managing your VuMarks in the Target Manager, see How To Work with VuMark Databases.
The database with the VuMark instances can be downloaded and imported as a package and database into Unity or a native development environment, or you may retrieve them programmatically using the VuMark Generation API. See Using the VuMark Generation API on how to do so.
See also Working with VuMarks in Unity for an introduction to importing and editing VuMarks.
Using Device Tracking with VuMarks
The Device Pose Observer improves tracking robustness by using features of the environment surrounding the target. It enables you to use even smaller targets and allows for tracking targets farther away from the camera. It also enables Extended Tracking where your target can be tracked even when the VuMark is no longer in the camera view.
See: Device Tracking
VuMark API Overview
The VuMark is created with the VuMark Observer. In addition, you will use a VuMark Observer Template that represents a set of VuMark instances. The template needs to be instantiated in order to track the VuMark instances. The corresponding Observations returns the tracking data of the VuMark.
For an overview of the VuMark API, please refer to the VuMark API Overview.