HOLOCEIVE / AR TRACKING SDK
Custom AR tracking integration
When a standard SDK does not fit your camera pipeline or target requirements, camera input, timing and coordinates need to work with your application. Work with Holoceive to test Holoceive SDK and plan the engine integration.
Discuss your target and integration ↗Define what your app needs to track
Image target tracking, object pose tracking and device motion tracking solve different problems. Describe what needs to remain aligned and relative to which coordinate frame. Holoceive SDK discussions currently focus on image and object tracking. For Web, smart glasses or VIO requirements, start with a custom integration consultation covering camera access, sensors and deployment constraints.
Specify camera input and timing
Specify frame format, resolution, orientation, timestamps, camera intrinsics if available, and ownership of capture and buffers. Explain whether another AR framework already controls the camera. Agree on how tracking results are timestamped and transformed into application coordinates, and how the application reacts to missing frames or tracking loss. Interfaces and delivery formats are defined around the application.
Handle app startup, pause and resume
For Unity, share the version, rendering pipeline, build targets and existing native plugins. For iOS and Android, include minimum OS and device requirements, build system constraints, camera permissions and suspend/resume behavior. Threading, resource cleanup and packaging should be part of the agreed integration deliverable. We test the proposed integration in your development environment.
From technical brief to production integration
Start with a short description of the target, the user interaction and the app environment. Together we define a scoped evaluation and acceptance criteria. The resulting integration proposal sets out target preparation, engine interfaces, application work, delivery milestones and maintenance responsibilities. The proposal explains what your team will receive and what each team will build.
Separate evaluation from production licensing
An evaluation plan identifies the targets, devices, sample data, test methods and acceptance criteria. Production discussion can then address app distribution, updates, support, target preparation and any custom work. Licensing and pricing are tailored to integration scope and deployment scale. Evaluation costs, delivery format and customization fees are agreed before paid implementation begins.
Considering a Vuforia or VisionLib alternative?
Bring the concrete limitation that led you to look elsewhere: target preparation, camera access, deployment constraints, tuning requirements or commercial terms. Compare candidates against the same acceptance tests and current vendor terms. Base your decision on tests with your own targets and devices. Our SDK alternatives page outlines the criteria to compare.
SDK alternatives ↗What to include in your evaluation request
- Tracking target and required output coordinate system
- Camera owner, frame pipeline and timing constraints
- Unity version or native build environment and target devices
- Offline, network, data handling and distribution requirements
- Evaluation criteria, expected maintenance and delivery timeline
Project-based integration with the Holoceive SDK engine team.