Let’s start with a message of mine on the HoloDevelopers Slack Community I wrote yesterday:
So I’m doing my first WebXR project now (on Babylon). I must say, I’m loving it. Having the power of every NPM module under the sun makes it extremely easy to integrate with things, and the async-by-default nature of the web just makes delivering content nice and simple. Deployment of new versions and things is also ridiculously simple, including things like multiple environments (dev/test/prod type thing) - it’s basically using the maturity of the web for immersive experiences.
Plus it’s easy to preview/emulate the base experience, and you can just use normal web stuff for debug/UI/options etc. It’s just an amazing fit.
I just felt like gushing. Go back to your normal lives 🙂
I think that captures it all quite nicely - really, you can stop reading here if you want - or the even more conscise version:
WebXR is a game-changer in immersive technologies, especially in enterprise.
Why? Read on.
Be warned this is developer centric. You won’t find many art or design opinions here.
In the user’s hands, faster
App deployment in enterprises right now is not a fun affair. Dealing with MDM, provisioning profiles with user-specific lists, not having the same hardware as the users (e.g. I run Windows - sorry iOS users, I can’t build your software) and/or manual installation steps - these slowdowns should be familiar to anyone deploying in an enterprise.
It’s especially problematic when you’re taking your product to customers - saying “Please download and install my app (after I get through the submission process), so I can sell you my widgets better” goes down like a lead balloon.
The web is another ballgame entirely. I can push to GitHub and my software is available in seconds (minutes if it gets complex).
Getting a user to test a new build is simply a matter of saying “press F5”. There you go, new version is just there. No updating from the app store required.
Want to take it to the public? Well you already have a website. There you go! Or, send them a link. Couldn’t be easier.
It’s also much simpler to have multiple streams - eg. “Dev”, “Test”, “MPE”, and “Production”. We’ve been doing multi-environment web pushes for years now. The tooling on your CI/CD platform of choice does this out of the box - simply see the “DevOps 101” part of the documentation.
In general, the move from App Dev to Web Dev means faster iterations, quicker feedback, and costs you less money. Why should immersive tech be any different?
Easy to pick up, for experts and newbies alike
Existing non-game developers can jump into WebXR relatively simply - no learning complex editor UIs, just grab a starter, download some assets and render it.
The Hello, World! of Augmented Reality - show an 3d model in your living room - is, well, easy. Literally some script includes, and a single HTML tag.
Hello World in a full-featured game engine isn’t much more complicated - BabylonJS does it in 20 lines of code.
And then you can build on top of it.
What’s your average enterprise running their entire operation on right now? If you answered anything but “web browser”, you’re wrong. Most people spend their days with a browser window/app opened. Internet-enabled technologies are enabling their day-to-day work.
Indeed, I work with someone who bought and uses a Chromebook as their daily workhorse, because they “don’t need anything but a browser”.
If you’re building out enterprise solutions, you will be integrating with these other services. Make it easier on yourself, and use the well-known web standards for this - what is better equipped for calling a JSON service: Unity, or a web browser?
Look, it’s a reality the NPM has a ridiculous number of packages. There’s an NPM package for everything. It has more than all the other languages combined.
Need to consume/render GIS data? TurfJS
Need to do machine learning? TensorFlow
And by using WebXR, you can have it in your project.
Better suited UI
A lot of enterprise experiences have a decent amount of pre-work before starting your immersive experience. Take VR training - you need to authenticate, select your training modules, configure any scenarios (maybe even review past ones first) - before you even begin. Once you’re done, you might need to review/comment on it, do quizzes, submit it.
I don’t want to do that in VR - noone likes typing on a VR keyboard, and any VR based menu system is going to be harder to learn than a web-based one.
So why not build that UI in HTML, and then pop the VR headset when you’re good to go? It’s all just web stuff - and a great way to bring in existing web development capabilities in your business.
Control your code
Using game engines (Unity, I’m looking at you) involves forsaking control. Want some behaviour in Unity? Inherit from MonoBehaviour, use these
magic specific and well-defined methods. Oh, and forget about dependency injection.
Don’t like the physics engine? Switch it out. Don’t like multiplayer system? I don’t have to wait for UNet to be deprecated - I can switch it out. All covered by open standards, and an NPM package (or 17) for each.
Async by default
Game engines usually support synchronous/embedded content first. You see it all the time - download an app, it’s 38GB. Or it’s 20MB, and you get a hefty download bar on first launch.
Bringing in dynamic content (like product models from a database) is often supported, but never the first thing in the documentation. Google it every time.
Moving to the web, you have no choice. Loading over HTTPS? Guess what, it’s asynchronous. You can’t avoid it.
Why is this a good thing? Well, it’s async by default - so you won’t fall into that trap of “Oh wait, I want that asset to be externally, I have to rejig my whole scene”. You’re already async.
It’s easy to make something that is asynchronous become synchronous/blocking - just “wait for load” before continuing. The reverse? Hard.
I’ve painted a fairly rosey picture of WebXR - I honestly believe that this standard is the tipping point for enterprise immersive tech uptake.
Ultimately, you will still need to test cross-device. You will still have to keep one-eye-in-the-headset when debugging. And you will also have to deal with browser quirks.
But you will be faster. You will get feedback quicker. It will be safer. You will have more control, and more options. It will be easier to pivot. You will have simpler access to SDKs and integrations. Playgrounding code will be trivial.
It’s a game changer.