Forever. Once you purchase a course you have access to the course materials and any updates to the course for as long as you'd like.

Each course has a specific course plan you can read by clicking on the "View content" button next to each course.

All our courses are designed for beginners as well as more seasoned web developers in mind. Previous Javascript knowledge is useful but not required above a very introductory level. You'll learn transferrable skills around 3D models, 3D spatial coordinates, meshes and materials, how to use web APIs, and much more.

The Intro to Advanced AR on the Web course does get into much more advanced material, but we will slowly build up towards it and explain the materials each step of the way.

The Intro to AR on the Web has English subtitles. We're working on finishing all the subtitles for our AR on the Web Masterclass. 

For the Intro to AR on the Web and Intro to Advanced AR on the Web courses: you can simulate WebXR apps using your desktop computer, but an Android or iOS device are highly suggested to experience true AR. Android devices should support ARCore (most do after 2016) and iOS devices should support ARKit (most phones and iPads do after 2017 as long as it's running iOS 11 or later).

Yes and no.

Right now you have to download a special browser WebXR Viewer (created by Mozilla and the one we use in this class) to make WebXR work on iOS. But if you use that browser the AR works beautifully and the code behind the apps are the same WebXR API. In fact, the same app will run perfectly on browsers on Android phones.

There are many signs that Apple is working to support the WebXR standard. And when they do, WebXR will fully work on iOS without the need for a special browser. 

The WebXR API is governed by W3C which is a consortium that decides on all web standards. They approve web standards and then different browsers (Chrome, Safari, Firefox, Internet Explorer) decide to implement those APIs in their own timelines. What is happening with the WebXR API is that Apple is moving quite slowly in implementing it. People speculate that this is because Apple prefers to invest in native APIs (like ARKit) to boost their own native apps and get people to buy iPhones.

While right now one has to download a special browser WebXR Viewer (created by Mozilla and the one we use in this class) to make WebXR work on iOS, there are many signs that Apple is working to support the WebXR standard. And when they do, WebXR will work on iOS.

Checkout these pages for their progress: page 1 and page 2. We explain this even further in the lesson "Your first experience with web AR on mobile iOS".

In a nutshell, Vectary, 8th wall, and AR.js DO NOT use the WebXR API.

8th wall: In the case of the 8th wall they have implemented their own SLAM library (a computer vision technique needed for AR) to make this work which is quite impressive. But essentially they are re-doing the wheel and implementing their own 3D AR environment for this to work.

Vectary: Vectary is not that advanced. They are good at helping you create 3D models, but the AR capabilities are limited to basically showing 3D models (no hit testing, no advanced manipulations, no complicated scenes). In fact it's very similar to a small free standard/feature that does work on iOS devices (after version 13) called Model Viewer. Vectary is sort of a glorified Model Viewer that charges on top.

AR.js: Libraries like AR.js do not even have a SLAM implementation. It means they are performing some traditional computer vision techniques but have no true understanding of 3D space.

A few more reasons we don't teach those libraries:

• They require payment. See Vectary pricing and 8th wall pricing. This is a big barrier for students who now have to pay for these libraries.

• 8th wall and Vectary are based on closed, proprietary APIs. The beauty of the web is that web APIs are developed in the open and can be discussed/developed/enhanced in the open. They don't cost anything and in time become widely supported standards. Both of these libraries are not extensible because they are controlled by two companies. On the one hand, it means they can make the experience really great. On the other, it means it will remain a closed ecosystem. Compare that to the open draft of the WebXR API.

Because we want the material we teach to be accessible to the most people and the most developers, we are believers in the long-term value of WebXR as opposed to other proprietary options (8th Wall, Vectary, etc.). We think over time, the benefits of open and free will win out (just like the web has flourished) and we will see amazing things and libraries built on top of WebXR.

Our long-term bet is WebXR will remain around far longer than other proprietary, paid standards.

Yes! Just send us an email for your certificate. The certificate is an electronic PDF with your name, completion date, and course name.

Within 7 days of the course start date, if you engage with the course materials and yet are unsatisfied in any way, we will refund your purchase.

Yes. Once you purchase the course you can log on to your account, click on the profile icon on the top right, and then click on the "Billing" dropdown button. There you'll find your invoice.

Absolutely, your payment is 100% safe. We use Podia to process all the payments and to host the course content. WebXR Academy itself does not store or have access to your credit card and payment information.

Just email us at hello@webxracademy.com!

We're always improving the courses and once you buy you get a lifetime access. If there's something you want to learn that isn't covered in the course content or syllabus please let us know and we'll upload new materials for you.

You can purchase a gift certificate for the Intro to AR on the Web course using this link.