HOLOCEIVE / AR TRACKING SDK
Image tracking SDK for Unity, iOS and Android
Connect printed artwork to an AR experience with Holoceive SDK, the native tracking engine from Holoceive. Discuss image tracking for acrylic stand artwork, cards and packaging, with Unity or native mobile integration shaped around your app.
Discuss your target and integration ↗From a printed image to an AR experience
- 01
Reference image
Artwork and physical dimensions define the target.
- 02
Camera tracking
The engine estimates the target’s position and orientation.
- 03
Your app
Your app places content relative to the tracked image.
Holoceive SDK provides the tracking engine and integration support. Your team can supply the AR content, or discuss application development with Holoceive.
Choose the tracking target that fits your product
| Target | Example | Integration |
|---|---|---|
| Printed image | Acrylic stand artwork, cards, package panels | Image tracking |
| Three-dimensional object | Figurines, product models, components | 3D object tracking |
What is an image tracking SDK?
An AR image tracking SDK finds a known image in the camera feed and estimates its position and orientation so an app can align digital content with the printed surface. Holoceive SDK brings this capability to Unity, iOS and Android projects, with target preparation and integration support from the team that develops the engine.
Image targets: start with the printed surface
Describe whether the target is artwork printed on an acrylic stand, a flat card, manual page, package panel or product label. Provide the final artwork and its physical dimensions if available. A digital design alone does not capture the effects of printing, glossy coatings, folds or changes in lighting. Include photographs of the physical print when possible, and identify which areas must remain visible.
Detection, pose tracking and recovery are separate tests
A successful initial detection is only one part of the experience. An evaluation should also measure how stable the overlay looks when the camera moves, when tracking is lost, and what happens when the image comes back into view. Define expected distance, viewing angle, motion and partial occlusion. Agree on the measurement method before comparing engines; frame rate alone does not describe tracking quality.
Unity and native mobile integration
For Unity, identify the Unity version, rendering pipeline and any existing AR or camera framework. For native iOS or Android, describe who owns the camera capture session and how frames and timestamps are made available. Agree on coordinate systems, image orientation and behavior when the app pauses or resumes. Work with the Holoceive SDK engine team to define the frame input, tracking output and application lifecycle for your integration.
Image tracking SDK or AR Foundation?
If your application already uses AR Foundation, first assess its image tracking against your actual targets and device coverage. A separate tracking engine is worth evaluating when you need different target behavior, camera integration or direct engineering involvement. Identify which system owns the camera and how target poses will reach the renderer before adding another SDK.
Build a repeatable target test
Use the same physical target, devices, camera settings and sequence of movements for each candidate. Include a normal-use sequence, a difficult-lighting sequence and a loss-and-recovery sequence. Record failures as well as successful runs. Compare initialization time, loss events and overlay stability alongside memory, battery and thermal constraints. Thresholds should come from your application, rather than an unrelated vendor demo.
No reference image yet?
You can begin with a description of the object or surface and the desired user interaction. A photo of a similar surface can help discuss feasibility, but it is not a substitute for testing the actual target. We will agree on what data is needed before an evaluation starts. If the target is a three-dimensional object rather than a planar print, use the object tracking guide instead.
3D object tracking SDK for Unity, iOS and Android ↗What to include in your evaluation request
- Target type, physical size and expected number of distinct images
- Artwork or photographs, if available; otherwise a description of the surface
- Devices, Unity or native platform, and camera framework
- Expected distance, viewing angles, lighting and recovery behavior
- Evaluation deadline, deployment size and any data-handling restrictions
Project-based integration with the Holoceive SDK engine team.