A-Frame v1.0.0 - WebXR Support, AR Mode
Today marks A-Frame’s fourth birthday. Four years ago, on December 16th, 2015, we released the first version of A-Frame to make it easier to build VR experiences and make the Web keep pace with the VR industry.
With the help of a community of hundreds of thousands of developers over the years, we’re releasing A-Frame v1.0.0 to support the coming out of the WebXR spec which has been under discussion for the past several years. The upgrade to A-Frame v1 and beyond will become necessary on more and more browsers as they deprecate WebVR and only support the WebXR specification.
To clear confusion, WebXR refers to both AR and VR support on the Web. To that end, we’ve included an AR mode out of the box in A-Frame for browsers that support ARCore and ARKit. In production, make sure to use HTTPS for VR and AR support.
We’d like to thank in part Google for providing a bit of funding to us at Supermedium to help develop and maintain WebXR support for A-Frame. And to thank people within Google, Oculus, and importantly the Web community for testing this version for us. We’ll continue to provide necessary updates to A-Frame.
We’d also like to celebrate now 300+ contributors, 10,000+ GitHub stars, and 300+ email subscribers to the A-Frame project.
If you’d like to continue to support us, please subscribe to the A-Frame newsletter where we’ll not only provide updates and showcase community projects, but requests for testing and user feedback support every now and then to keep us going in this grassroots project.
Read the release notes and changelog.
A-Frame 1.0.0 is out! 🥳 With full WebXR support shipping now in Chrome 79 and Oculus Browser stable channels. Deliver VR experiences instantaneously to millions of users today! Happy immersive Christmas! 🎄
— A-Frame (@aframevr) December 16, 2019
We're still at it! Today marks the exact date of @aframevr's fourth birthday, and we're excited to release v1 with the help of the #WebVR community. https://t.co/rlvFSpjBvu https://t.co/DHgRoEgb9f
— Supermedium (@supermediumvr) December 16, 2019
For those who are using AR.js with #aframe in WebAR apps, please import latest #aframe, v1.0.0 has been shipped 🚀
— Nicolò Carpignoli (@nicolocarp) <a href=”
This will avoid problems with new Chrome 79 that has WebXR Device API enabled by default.
Thanks to @aframevr team for the great work. It's outstanding.?ref_src=twsrc%5Etfw”>December 15, 2019For those who are using AR.js with #aframe in WebAR apps, please import latest #aframe, v1.0.0 has been shipped 🚀
— Nicolò Carpignoli (@nicolocarp) December 15, 2019
This will avoid problems with new Chrome 79 that has WebXR Device API enabled by default.
Thanks to @aframevr team for the great work. It's outstanding.
Hey devs! 👋 Remember to serve your content over HTTPS to enter VR mode in Chrome with A-Frame 1.0.0. WebXR is not available over HTTP.
— A-Frame (@aframevr) December 16, 2019
🎉I'm SUPER excited for the 1.0.0 release of @aframevr now that #WebXR is shipping in Chrome 79🎉
— Kent Bye VoicesOfVR (@kentbye) December 16, 2019
There's SO much potential of merging spatial computing with the open web to form the #widerweb & early seeds for what may become "The Metaverse."
Congrats to the @supermediumvr team! https://t.co/FuEgbBstFS