It’s great to hear that you’re developing some world tracked experiences - please allow me to clarify some confusion between our world tracking types
First up is our traditional World Tracking - this is intended for native app deployments (Zappar App, custom app, app embed) only. The reason for this is because with the traditional World Tracking implementation, we require AR Core or AR Kit (which allows us to get important tracking information from the device).
Due to web browser restrictions, we are unable to use AR Core or AR Kit in the web. This means that if a device does not support ARKit or ARCore (or you are launching a traditional World Tracking experience in the web browser), traditional World Tracked experiences will use the device’s gyro to update its orientation. This is why you may see the ‘Unsupported’ dialog.
You can learn more about World Tracking for native applications on our documentation here
That leads us onto Instant World Tracking, which is a kind of world tracking type which we built for WebAR (AR in the web browser). Unlike traditional World Tracking for native apps, Instant World Tracking doesn’t rely on ARCore or ARKit and so is supported by the vast majority of mobile browsers.
To use this tracking type, simply go to our documentation site here and download the template. Then, once you have previewed or published your ZapWorks Studio project containing Instant World Tracking, you’ll need to scan the experience by using one of the WebAR sites listed below:
https://arweb.app (Lite Branded Distribution)
https://beta.zappar.app (Beta Zappar branded Distribution)
An Enhanced WebAR Distribution site
Hopefully this is helpful!