We built Launch to be better.
After creating almost 100 AR experiences, we took a long, hard look at the pain-points we felt with existing WebAR SDKs. We built Launch to be cheaper, more reliable, and all-around better.
No more low FPS & drift from Javascript tracking libraries.
Industry-standard, rock-solid, world tracking via ARCore and ARKit.
We won't force you to use an online code editor or heavily limited 3D editor.
Write code with your preferred tools, and host your code wherever you want. Use open standards with no lock-in.
Avoid expensive, variable or hidden monthly fees.
Pricing with no unpleasant surprises: A fixed monthly cost at a fraction of the price of other WebAR SDKs.
Fixed low cost. No surprises.
Get started for free, then decide your project plan based on the needs & duration of your project. We don't charge for views.
Developer
$0
Start building for free. You’ll be able to upgrade if you start getting large numbers of views.
- 5k views/month
- "Powered by Variant" watermark
- Default app card
- Email Support
Basic
$299 / project
Perfect if you are building your own AR experience.
- Unlimited views
- Default app card
- Email Support
Pro
$599 / project
Ideal for building fully-customisable projects for clients.
- Unlimited views
- Marker Tracking (Coming Soon)
- Fully customisable app card
- Priority Support
Frequently asked questions
If you have anything else you want to ask, reach out to us.
How does Variant Launch work?
Variant Launch uses a combination of Android's native AR tracking, and an iOS feature called App Clips that seamlessly downloads the Variant Launch viewer and displays your experience.
Does the user need to download an app?
Nope! The user just needs to scan a QR code or tap a button, as they would with any WebXR experience. The Variant Launch viewer is downloaded silently in the background, and the user is taken to your experience.
How does the Android/iOS UX differ when using a QR code?
There is almost no difference in UX when using a QR code. When scanning the code in each platform, the user is taken directly to your website, with WebXR available. This is why we recommend QR as the preferred discovery method for your experience.
How does the Android/iOS UX differ when the user starts on my website?
On Android the user can tap a button to launch your experience in standard WebXR. On iOS the user must tap an App Clip prompt to launch the experience. You control when the prompt is presented to the user, and depending on your plan you can also customise the look and feel of the App Clip prompt.
What are the limitations to this approach?
To trigger the App Clip prompt, the user must be redirected to a Variant Launch page. Currently the options for customising this page are limited, but we are working on expanding customisability. The user must also be in a Safari browser session to launch the app. We detect the most popular browsers and apps, and direct users how to best access the App Clip.
Is WebXR support on Android universal?
WebXR support on Android varies depending on device and browser, but the vast majority of Android phone users will be able to launch WebXR from their browser