Peter Howell (@peterhowell) header
Peter Howell (@peterhowell) profile picture

Sr. Engineer @getsupernatural. Ex-@meta - XR & Wearables. 2x Girl Dad. Opinions my own.

Redondo Beach, CA
Joined November 2008
Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)Photo by Peter Howell (@peterhowell)
Thrilled to help re-launch Supernatural as independent. The team poured their heart and soul into this. More to come. 😎 @getsupernatural
Supernatural is back! New independent company is live today! If you ever used Supernatural, transfer and save your history now: wearesupernatural.com/import…
4
153
Three razors I’ve been using to kill product ideas fast and seek durability 1.) Will the frontier labs swallow this as models and harnesses grow in capability? 2.) Is someone else already doing this? 3.) Can this be copied easily?
125
I got Doom 3 running on Meta Ray-Ban Display through the Web Apps Developer Preview. Here's what I learned model instrumentation, tool use and what I consider to be a lowering of the bar of systems "too complicated" to touch. Repo: github.com/phdev/doom3-rayba… Recently, I ported Quake II. The lesson: AI coding harnesses can now reach the engine layer. So I looked for the ceiling with Doom 3’s advanced idTech 4 engine. The port is the testbed. The real work was model instrumentation: building the model’s eyes and then brokering their captures back into context. I started from dhewm3, the open-source Doom 3 port. There was no real complete web build. The GL path had a chunky-tile flicker on Glasses and mobile Chrome / WebKit GPU stacks that no GL-side fix could cure, so Claude Fable/Opus and I built a WebGPU renderer. The proof: a determinism self-test showed byte-identical WebGPU output on Android & iOS while GL flickered on the same device. That mattered because the model had no native view of the running thing. Canvas readback and headless screenshots of a WebGPU canvas came back black. A headed browser could show the frame, but to close the loop we had to screenshot headed Chrome or move the instrument inside the engine: byte-comparing two renders without reading the canvas back. You can’t fix what you can’t see and off-the-shelf tools were blind to WebGPU. So the work was building instruments that weren’t blind: determinism self-tests, shader-channel probes, in-engine debug modes, and a CDP/console bridge. Once those made failures visible (Draw-record cap dropping geometry, NaNs poisoning the lit-pass shader) Claude Fable/Opus could observe, reproduce, and fix them fairly quickly. Getting it running on compute constrained glasses was its own grind. The Chrome / WebKit GPU process hit 1.7 GB until delta vertex uploads, redundant-submit skips, and bind-group eviction stopped tab-kills. About 45% of CPU was clock reads in a busy-wait loop. Textures were resident twice until we cut duplicates. Boot went from 10+ minutes to ~30 seconds by baking binary geometry and nav-mesh caches, replacing ASCII parse, and deferring an 8.6s main-menu parse the web build never shows. Download came down from 1.5GB to ~20 MB! via a dependency-aware pak and per-area far-geometry streaming. Net net: The set of systems “too complex to touch” is shrinking fast. Not only because models are getting smarter but they empower us to build tools that "show" them what they need to see. To try: Buy a copy of Doom 3 (gog.com), point your coding harness at the repo README, and give it a whirl. Bonus: the same build runs in mobile and desktop Safari and Chrome, downloads faster, and runs @ 60 fps. 😎 @ID_AA_Carmack
5
1
5
1,110
Badly needed in Claude Design: Keep running when iOS Safari is in background.
70
I got Quake II running on Meta Ray-Ban Display through the Web Apps Developer Preview. The port itself isn’t the interesting part. What it taught me about AI-assisted development for open-source software on new form factors is. Four things stood out: 🧵 Repo on my GitHub: github.com/phdev/glquake2-ra…
8
5
65
5,072
4.) Asset chunking matters more than it looks. Large monolithic downloads are fragile on bandwidth-constrained devices. Smaller, dependency-aware chunks download reliably and progressively.
1
3
139
The takeaway: harnesses are now good enough to work at the engine layer. This makes open-source software far more adaptable to hardware it was never written for. For anyone building developer platforms on novel devices, that shifts what’s worth attempting.
2
5
123
Peter Howell retweeted
Developer Preview for Meta Ray-Ban Display is rolling out. 👓📷 Build web apps for display glasses with HTML, CSS, and JavaScript, or extend your mobile apps with the Meta Wearables Device Access Toolkit. Start building today 📷👉 developers.meta.com/blog/bui…
28
66
30
408
80,337
Announcing two build paths for Meta Ray-Ban Display in Developer Preview. Now is the time to starting building the future of Wearables with rich, visual experiences. 🕶️ Device Access Toolkit — Extend mobile applications to Display 🖼️ Web Apps — Build using standard web tech
The gap between idea and prototype has never been smaller. Add glasses and inputs like the Neural Band, and it feels like the early days of building in a way we haven't seen in over a decade. We're rolling out web apps and a mobile SDK on Meta Ray-Ban Display. Developer Preview to start, but you can build now. Here's one called Darkroom Buddy which guides you through developing film. Glanceable steps when you need them, the kind of experience that only makes sense on glasses.
2
2
337
We are announcing steps to a more open platform to bring the power of mixed reality to as many people as possible. We’re making it easier for you to build and reach your audiences on our platform. ocul.us/3xGRM9s
1
4
3
23
3,466
Peter Howell retweeted
Mr @jurney has just announced The Oculus Publishing Ignition program, a multi-million dollar fund designed for new VR/MR startups. If you're a veteran game dev that got laid off recently and you're thinking about a startup, check this out. developer.oculus.com/blog/in…
4
20
4
75
12,171
We announced a lot of XR topics at Meta Connect 2023. IMO, Meta XR Sim is the most important one, not just this year but maybe ever. Here's a quick thread on its featureset. Xiang is the creator of Meta XR Sim, so everyone should send him your feature requests, bugs, and more!
Introducing the Meta XR Simulator - the first of its class to be certified as an OpenXR-conformant runtime, and simulates Meta Quest/Rift headsets. Supports Unity, Unreal & native C++. Start developing your VR/MR apps even without a headset! Get it here: developer.oculus.com/downloa…
3
12
92
18,625
Peter Howell retweeted
TODAY IS THE DAY 📣 #MetaQuest3 is HERE. 🎨 Full-color passthrough 🔮 Breakthrough mixed reality  🤩 500+ immersive apps All that’s missing is YOU. Order now: metaque.st/Order
159
167
31
854
153,872
Want to get the most of out Quest 3 perf & graphics? Definitely watch AR Schleicher's session tomorrow Thurs, 9/28 @ 10am.
I'll also be speaking as part of Meta Connect this year! Don't miss it. 🙂 #MetaEmployee
2
3
838