What if, when you needed something organic, your design tool just did the physics? Right now anything that should bend, squish or react to another shape, you fake by hand with the pen tool. So I have been building a tool where shapes are actually soft.
API design still matters.
Built ComponentCode, the component next to the code that uses it, every value live. Helps me feel whether an agent gave me a good API or just a working one.
@joshpuckett Agree. In my experience though, the extra work that makes something great often goes unnoticed unless you know where to look. Curious if you feel the same?
Well, I didn't dig too deep into it. I just pointed Grok bot at those folders and initially asked it to generate recordings. I assumed it would spin up a VM with Flash Player and screen record the sites.
I noticed it was running them directly in a modern browser using Ruffle. So I started asking it to generate builds I could run and deploy myself.
Some things came up slightly different or broken, but a bit of back and forth and it got it right with very little effort. The major gaps were things like no webcam (Camera), so AR and motion tracking did not translate and a few renderer bugs with giant bitmaps and multiply blends looking lighter.
Performance is noticeably worse in some cases, it gets stuck sometimes, and Ruffle version matters a lot. I feel there might be room for optimisations that I didn't run or ask for.
Here's an example of a full site with quite a lot going on (heavy assets loading, lots of animations and code, nested movieclips, and so on):
https://t.co/uX5rsuWMqO
@seb__design Agreed. The initial cursor is ‘grab’ (not visible in the video) to help with that. The interaction came from this idea of having some sort of switch component that would take less space.