This is super cool, and I loved seeing the FPS stay locked at 120 on my phone. I didn't see this on the website, but do you have any docs that detail how your library compares to other popular options such as Three, Babylon, etc? Definitely giving this a try today.

One thing I noticed is that the "hover" functionality in most of the demos doesn't behave well on mobile. Taps don't stay active for long after interacting with something. Not sure if this is intentional or just a browser compatibility quirk (Fennec on Android 17). Happy to make a contribution if it should be a little more persistent!

One of the first things i did was to "gap analysis" with existing libs to see if i could find a niche as I don't want to overlap three.js too much...

The full source on github has a bunch of agent tests that compare running tasks with phoria and three.js. It comes out well, with the agents able to build with both (obviously three because it's TRAINED on that, but I provide enough in llms.txt etc for phoria) and phoria code is ~50% smaller for the same task!

I'll have a look at the hover, always a tricky thing on phones/pads