Mira Developer Portal

The Mira Labs Developer Hub

Welcome to the Mira Labs developer hub. You'll find comprehensive guides and documentation to help you start working with the Mira headset as quickly as possible, as well as support if you get stuck. Let's jump right in!

Download the SDK

Tracking Best Practices

Tracking Best Practices
Due to the angle of the phone in the headset, the “trackable area” is angled approximately 30 degrees down from the user’s line of sight. When the virtual image is placed directly on the tracker, the user turns their head to see the content, and the marker is no longer in the trackable area. It can feel like the user is chasing the image.

One UX solution is to place your key content 3-5 inches above the surface of the tracker. This allows the user to keep the marker within the trackable range, while keeping the content within their field of view. To strengthen the relationship between the content and the marker, it is advisable to place the key content on a translucent “stand”

If the projected content covers most of the tracker - for instance, in the case of the stands/podiums mentioned above, it is imperative to keep them translucent. If the projected image is both large and bright/opaque, the tracking will be lost in dark lighting. This is due to the autoexposure blowing out the projected image on the display, and obscuring the camera’s view of the tracker. If the virtual image is relatively large, and will be placed right on the surface of the tracker, it is recommended to keep the material dark or transparent. Smaller objects can certainly be bright and opaque, to take advantage of the vivid display

Updated less than a minute ago

Tracking Best Practices

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.