Added interaction support to the HTMLTexture (html-in-canvas) example.

more html-in-canvas slop

Fun hack: A new way to inspect web with... the html-in-canvas APIshow more

we praise html-in-canvas ✨

html-in-canvas can't ship fast enough

html-in-canvas API is shattering my expectations

Tried combining Three.js raymarching with html-in-canvas.

The web is fun again. HTML-in-canvas is insane. Made... with Omma.show more

This is soooo coool The first HTML-in-canvas Component Library... is hereshow more

With html-in-canvas, you can make shader-powered page transitions

ummm you can create some obnoxiously cool focus rings... with the new HTML-in-Canvas APIshow more

human <> machine html-in-canvas transition should we ship this... on the new docs?show more

This has to be the creepiest example I've done... so far.show more

Card transition experiment with React Three Fiber + html-in-canvas.... Try it here: Needs Chrome Canary for the interactive cards.show more

Finally added a lap timer ⏱️ 👀 🕹️ It'll... remember the best times for each track.show more

added this button interaction to my portfolio (Stole or... got the inspiration somewhere)show more

DOM3 is made from HTML, CSS and Javascript, closer... to a document than a canvas. It's a strange contemporary material that shapes much of our digital lives. The rhythm of endless creation and deletion in DOM3 is a self-driving version of what happens when you browse the web. "The Document Object Model (DOM) connects web pages to scripts or programming languages by representing the structure of a document—such as the HTML representing a web page—in memory." A html element, and a rectangle on a canvas, are not the same thing. It's a different material. Even if it all ends up controlling the same pixels, the process is different. The html element kind of actually exists, in this abstract context of a document object model. And in memory, in the moment. If it was possible to measure its weight, it would be heavier than a pixel on a canvas.show more

Fine, I'll bite. Paper will never, ever, eat Figma's... lunch. Not Paper, not Claude Design, not Google Stitch, not V0, bolt, lovable, base44 or any of the HTML/CSS-based canvas. Why? The number one reason: Performance. Paper struggles at 2-5K elements of plain rectangles For comparison, in the attached video: a small, early-stage exploration canvas with 13K elements. Real-world projects are tens of thousands sometimes hundreds of thousands of elements. Why do you think Figma has a hyper-optimized webGL rendering engine? It would've been way easier to have an HTML/CSS-based canvas if that was feasible. Figma's money comes from tens of thousands of organizations where *at the very minimum* need to support these canvas sizes. Does it hurt Figma that many individuals and small teams are switching to other tools? arguable. Does Paper have better *MCP support* than Figma*? 1000 percent. Not even close. but MCP support != better overall or even an option for most. I'm not saying Figma's lunch won't be eaten. I have a huge horse in that game, betting it will be. I'm saying *HTML/CSS-based canvases, specifically* won't.show more

Slide to pay component, added keyboard interaction too this... time Designed in Paper, animations with Motionshow more

Just added an example of how to implement a... simple gaze tracking task on the Apptronik robot in mink:show more

Today we're stoked to have Vittorio Retrivi from basement.studio... share an incredible exploration of the emerging HTML in Canvas proposal. From shader powered UI effects to interactive 3D interfaces, this article is packed with inspiring experiments:show more