explainers

> they're trying to add a <model> tag and standard 3D model file format to HTML right now. To clarify, Apple made a proposal[0] which got no real traction. It has migrated[1] to a Javascript API[2] [0] https://github.com/WebKit/explainers/tree/main/model [1] https://www.w3.org/community/immersive-web/ [2] https://github.com/immersive-web/webxr

Hi there! USDZ is the format that Apple is backing for VR/AR delivery (developed by Pixar)[1]. We're betting that it is what is going to be used in any Apple headset. Right now you can't easily view USDZs in the browser (the format is a moving target), however Apple is making strides to make it available with the proposed Model element[2]. We were doing some USDZ --> GLTF converstion (GLTF being a format that will work in the browser), but it is jankey (technical term). I have not tried an iPhone 6 yet. I will have to pry it from my children's hands and remove a layer of cheese and excretions before I do. I've made a video on how to do this via the browser here[3]. TBH, the experience a heap better in the iOS App (currently in testflight) [4]. [1] https://graphics.pixar.com/usd/release/wp_usdz.html (seem to have cert issues) [2] https://g

Historically perhaps! I'm not sure how so. These days, the only entity I'm aware of trying to help the web forward with 3D that I have seen is a company I criticize frequently for holding the web back, Apple. They have been working to add a <model> element[1]. I'm not sure exactly what the intent is, but off the bat, one interesting contrast was that VRML feels like it's own totalizing element, defines a whole environment. Whereas model feels like a thing on a page. If you have a tree, ground, and a house, those are three models on a page, potentially, I hope, which is something I never felt like the old attempts appreciated: they were the Flash/Applet model, a sub-experience. Also happy to see Apple add BroadcastChannel and File System Access in Safari tech preview 131. I'm still uncomfortable/alarmed having a general purpose device that

> In our "current world", if you want a 3D viewer, you use WebGL and Javascript, and voila, what you get is what you see in all browsers that support WebGL. Under "Considered Alternatives" [0] > 4. Do not add a new element. Pass enough data to WebGL to render accurately > As noted above, this would require any site that wants to use an AR experience to request and have the user trust that site enough to allow them access to the camera stream as well as other information. A new element allows this use case without requiring the user to make that decision. [0] https://github.com/WebKit/explainers/tree/main/model#conside...

"Native apps don't usually remain authenticated" Thanks for the correction, I admit I have limited knowledge of production ready native app development! As with the UI issue, a PWA developer could still use the JS crypto APIs to roll their own secure store for credentials, or store something similar to an API key issued on successful authentication? Handling this kind of data correctly has a lot of pitfalls, which is likely why most PWAs still use standard authentication processes. There are APIs and specs [0] [1] [2] that have been floating about for at least the last couple of years which aim to solve credential and authentication management in a more formal way in the browser, but as with many of these features, they're slower moving than the native SDKs. I still don't believe that makes it impossible to achieve a similar flow in a PWA