Some of these are genuinely nice. I really like the action slide-out, the wall reveal, and the slide-off reveal.
Unfortunately for a thing whose core job is polished UI, there's still quite a lot of polish needed before I would be willing to implement any of this in my UI
To name a few :
- the swap icon state theme preview switcher cascades the element brightness rather than fading them together.
- The confirm reveal has something wrong with the spring every third or fourth click, which is strange
- Cards: the stacked deck cycle. When you click Next, it doesn't draw the top card.
- The shared element expand option: when you minimize, the spring dampening pushes the components outside of the container.
- Swipe to dismiss causes the container to temporarily show a scroll bar.
I just set up penpot on a fly.io and connect to it with mcp -and- a browser-use-tool.. because of network weirdness and serverles platforms.. and then i can get the best of both worlds, of a structured ui design tool, and a flexible adaptive chat interface. couple that with .. image generation tools, and code execution for converting generated pngs to svgs, and I think I came up with something pretty neat.
I wanted to say that some animations look choppy, but it's yet again the reduce-motion css feature that maps to Windows's Animation Effects knob, which is completely outrageous.
Love these but curious: they sell access to this UI but can't I point an agent at this and have it copy these? Or is it better quality outputs to use the MCP?
Thanks! Me and the co-founder of the project built Flowbite previously so we have some experience in the UI/UX field. I think that as with anything you can copy it, but your agent will be pointed to an HTML+CSS structure, rather than the natural language structure of our prompts/MCP context. Plus, you can support the work of two fellow humans.
You get quite a bit more than that, including access to the MCP server. We are boostraped, no VC to back us so it's the only way we can make this project sustainable.
* toggle animation on the heart moves the same direction for add and subtract (confusing)
* hold-to-trigger indicator is covered by finger on touch screen
* remove button confirmation can be accidentally confirmed by double click
(I stopped looking after this)
Unfortunately for a thing whose core job is polished UI, there's still quite a lot of polish needed before I would be willing to implement any of this in my UI To name a few : - the swap icon state theme preview switcher cascades the element brightness rather than fading them together. - The confirm reveal has something wrong with the spring every third or fourth click, which is strange - Cards: the stacked deck cycle. When you click Next, it doesn't draw the top card. - The shared element expand option: when you minimize, the spring dampening pushes the components outside of the container. - Swipe to dismiss causes the container to temporarily show a scroll bar.
I do love some of these examples, but, and as others noticed, they do lack polish.