Ok, so I got BabylonNative to run on my iPhone (looks good) and on a VR headset (Samsung Odyssey using Windows Mixed Reality), so now that I know that it works, and has decent performance, I’m going to try and get Cryptovoxels running on BabylonNative (initially so I can put it in the WindowsMR store).
This is awesome! Just as a quick note in case you weren’t aware, Babylon Native intentionally avoids bringing in implementations of DOM elements as much as possible — hence the absence of Canvas and XMLHttpRequest. That’s just the core repo, though; plugins and polyfills are specifically intended to make it easy to bring in anything you want.
If you do end up wanting to make extension components, we have a relatively new quick-start guide in our docs for a pretty easy way to develop them. This also touches on a conversation about Babylon Native extension conventions that we haven’t explored yet. We want to make it as easy as possible for people to develop, use, and share extensions, but we don’t have any established conventions or known preferences for how people might want to go about that. Thus, if you do end up going down that road, we’d love to get your input on what the best approach might be!