Comment by merelysounds

There are a bunch of those for free no ? Rails blocks (paid, about the same price as this Rails UI), Ruby UI (MIT licensed), I think I saw a couple more here.

Pricing per seat makes little sense for a component library. It forces every party involved in building an application to acquire a license, not just a designer who might otherwise have been hired once to provide the assets. Seat-based pricing suits tools people daily drive (Figma, Slack), whereas asset libraries are better priced by what you ship with them.

A more natural unit for pricing would be per domain, application, environment, or similar.

That said, I'm aware several UI frameworks have moved toward seat-based licensing recently, so it must be working for them in some sense.

> 25% of a decked out developer Macbook for something that sets the look and feel of an app and forestalls an entire designer hire is an unseriously low price.

Potential value bounds the price upper end, but alternatives set what the customer will actually pay. There are much more comprehensive tools of similar nature that are offered for free.

The (somewhat) unique value proposition it offers is in how it integrates into Rails, saving an hour of a developer's time — or a couple of minutes of an LLM's time, if the slot machine happens to work in your favour on that particular spin — required to manually do it themselves. That's worth something, but if you go too high it soon becomes more cost effective to just pay someone to put in that hour.

The repo was created in May 2023, and it seems like the bulk of commits were made in 2024, before vibe coding was really a thing. I think it's pretty harsh to dismiss projects in this manner.