In reply to Peter Shaw.

Hi Peter! Thanks for reading. I’m trying to understand where the flaw is in regards to the prototypes and ideas above. I always love discussing this topic, so I’ll address your points there relative to XR and native apps. :)

1. This content will always be dear delivered over the web.
Absolutely no argument from me on that. No matter the tech, we will always need some way reach the web, but currently we focus a lot on end content being saved as HTML. That limits the extendability of the content. More on that below...
2. The only standardised way if navigating that will be a browser (which are are improving rapidly)
3. That browser will consume HTML and successor HTML like markups (eg Svg, Vrml)

I wholeheartedly believe browsers will remain THE dominant tool for displaying web content. I don’t think many folks can argue against that. In my illustrations above, I’m simply showing how markup is an obstacle currently, and how defining context, much like how Gutenberg does with attributes, is important. This is not to say we shouldn’t render the content down to HTML in the front end any differently. The idea here is to unify both your content and design decisions.

The one thing developing still are standards between web and XR tech. I encourage you to check out OpenXR ( https://www.khronos.org/openxr/ ) and the standards they are attempting to set on a hardware level. This all eventually goes back to the browser model however, context for content is still needed and different in every environment.
XR is throwing so many new environments into the mix (MR/AR/VR/etc) and it’s hard to stay flexible with the tech advancements every few months. This notion of using Gutenberg blocks to expose only context and content is important to stay nimble with the changes.

I hope my points above do not support an idea that we will one day be exclusively fully headless on the browser level. My illustration here is only that we are already primed to unify our content to native app experiences; and currently, the XR market is heavily positioned in native apps. I think Aframe and Mozilla Hubs are doing an excellent job of showing the potential and need for browser support, which is in turn influencing those OpenXR standards.