Universal SDK and device engineering
The Universal SDK programme aims to connect software components, app integration, device-specific services and repeatable build workflows across supported platforms.
A common engineering integration layer
A cross-platform SDK can define common data and behavior contracts while delegating camera access, spatial registration, storage, identity and device-specific permissions to the underlying platform. Shared APIs do not make iOS, Android, Windows and other devices identical; each release needs its own supported capabilities and test record.
Build, package and evidence
A dependable workflow needs version identity, source provenance, signing, reproducible builds, device installation, runtime diagnostics and an auditable record of failed as well as passing checks. A successful compilation is different from a successful installation, feature qualification and end-to-end user acceptance.
Field applications and Bridge
HuntAR, SearchAR, HikeAR and related applications can use common spatial or rights-aware services where justified. BTG Bridge connection services may share support and authorization interfaces, but a general SDK contract does not establish that an external provider or a protected device is already supported.
Protected source and owner authorization
BTG’s SDK and engineering control system are proprietary. Public technical documentation explains deployment boundaries and adoption requirements without exposing signing credentials, internal support access, machine control endpoints or private repository source. Sensitive actions depend on owner-approved and authenticated access.
Qualification expectations
A supported SDK release should identify package and build versions, operating systems, device compatibility, authorized integration tests, known limitations, security controls and documented support contacts. This information is version-specific and should be presented in a release evidence record when available.