It looks good, but I'll be honest, it's hard for me to consider $299/$799 if I can buy a beautiful theme off of somewhere like ThemeForest for $20 or $30 and toss it into an LLM to get the files parsed into components and templates.
That's fair. Probably not a good fit for you then. I wanted to keep the human element alive where I could with this project and I know AI will likely take all our jobs, so be it. It's solving a need for me when it comes to building ideas quickly so I figured maybe others would benefit. I'm a product designer by day and love building front-ends so it's also a passion project.
You don’t even need to do that anymore. It’s capable of visiting those sites and just copying the components look and feel. Try it. Ask it to make a template based on a theme you found and show it the link to the demo and BaM! You got something similar.
It's really weird to me how people on this site used to have a much bigger problem with ripping off other people's designs and work, but the minute it became turnkey it was like, "sorry art nerd guess you starve now roll coal".
This definitely does fill a gap that Rails has. I love using it but man I can't make a nice looking front end to save my life. We've used Tailwind UI a ton but thats kind of a foot gun because you end up slightly tweaking classes all over the place if you're not disciplined.
I've fiddled with Open Props [0] a bit lately, seems like a nice middle ground! Colours/fonts/spacing/etc that look nice together are there, but it's still up to you to use them. (And you're still writing CSS, so might be a deal breaker if that's the part of tailwind you like... but CSS is rather nice nowadays.)
I used this about a year ago when I went through a short Rails phase. I was a bit surprised not to see more Rails-specific UI libraries considering how batteries-included the rest of the framework is, and at the time I didn't really 'get' tailwind. I'm not in a Rails phase anymore, but nice work on the library!
Hey, thanks for giving it a shot! Agree on the UI front. It seems to be the most "unconventional" thing about the framework. Always struck me as odd, but I suppose it makes sense given how an app needs to adapt to a brand, audience, and market.
I've launched 3 Rails SaaS products in the last 6 months, all profitable. In the world of LLMs things like this feel less valuable. I can kick off a Claude Code prompt and in 1 hour have a decent design system with Rails components.
Things like this likely need to be AI-first moving forward. This feels built for humans.
That's fair. I think there's a future where some folks won't want AI to generate all the things. I replied to another comment before but this was very little AI minus some architecture direction of the underlying ruby gem.
Personally, if I feel like you vibe coded your SaaS I’m probably not gonna pay for it. You can obviously tell when a project is vibe coded just based on the way it looks, the weird bugs you see and the poor documentation.
There’s definitely a market for good looking UI that actually works and stands out from the vibe coded junk. Artisanal corn fed UI I guess.
Same here. This was human driven UI. I used AI sparingly for mostly architecture decisions on the gem. Otherwise all by hand. I'm a product designer by trade.
Maybe they used AI to make this ? But really though I hope they didn't and did some of designing themselves... I'm worried we are approaching a world where we never get new human designs just regurgitated designs from pre 2025.
I used AI sparingly actually. Mostly just some help for Ruby gem architecture and how to approach swapping themes on the fly otherwise all me. I'm a product designer by day so this stuff I do constantly.
Definitely aware. I built it to scratch my own itch to be honest. I'm going the non AI route with it. Lotta slop out there. I'm sure it will improve but I'm fine with this being a side gig.
Agreed - particularly because there is an example of a login box and the screenshot of that is far more prominent than the rest of the design.
I don't think the demo should overpower the landing page.
And then it goes straight into themes. If I'm a Rails developer I'm not looking at theming, I'm looking for a conventional UI system that fits into Rails - stimulus, Hotwire, all that.
As far as I know, this site so far is just a bunch of specialised scaffolds for certain use-cases, but Rails itself has been capable of that the entire time.
Good feedback! This is a common misconception about themes. Rails UI is more of a hybrid as it offers UI components plus optional pages that build out a theme using those components.
You can either take the pages and tweak them for your own use case, or just use the UI components and skip the theme entirely. If you get a chance, try the free Ruby gem to see what I mean.
The login box is maybe confusing or maybe I'm misunderstanding you, it's actually UI for a login box, not actually where you login. I agree this area could be tightened up.
Did a quick search and no-one has flagged a11y/colour/contrast but the animating effect for the brand colour often had a colour contrast around the 1.0 range.
Yeah pretty much didn't care about it for the sake of effect. That's a big no no I know. The website isn't really the focus as the goods in the ruby gem are more of the focus. Consider railsui.com a billboard if you will.
If you’re showing off a UI framework, I shouldn’t be accidentally scrolling left and right on the page on mobile / my iPhone. Couldn’t be bothered to scroll down the page to look at components while accidentally activating horizontal scrolling.
This is interesting to me as someone who worked with Rails a good deal back in the day and has interest in picking it back up.
Any chance of some themes that bring in a little dimension? Doesn't have to be early 2010s Bootstrap or anything but some subtle, crisp drop shadows and gentle gradients would be welcome.
Additionally, is unused Tailwind CSS shaken out or does it all come along for the ride?
Yes, it's on my radar to add more unique designs to the mix. Less typical, if that makes sense. For now, it's mostly a huge head start if you're building quickly.
And yes, unused Tailwind CSS is automatically extracted when it's built. For Rails, we use the tailwindcss-rails gem as a dependency for Rails UI, which JustWorks™.
i don't get these types of products anymore. i think they're useful in their own way, but i can literally create styles with claude/gemini in a heartbeat and not have to pay some insane fee.
Fair enough. Yes, AI can one-shot a lot now, but I sort of think human-coded stuff has its place. Having done both, I'm most often cleaning up the AI UI that did a piss poor job. I'm sure it can improve in time, though. I built this to scratch my own itch as I'm doing a lot of 0-1 development on ideas.
My guess is there's a lot of shops that don't want to mess with prompting AI to get to something clean and usable, and would rather just save money and pay the fee.
Hey! A lot of the UI on the theme preview site and on railsui.com isn’t fully functional. It’s mostly there to show the design and layout of the components, not the underlying logic. The railsui gem itself has more complete, working components and pages.
I wish I could use this – unfortunately UI frameworks are a political problem at every company I've worked at. The designers feel undermined or threatened by it, and product owners want to dictate design. Despite the massive productivity benefits of a UI framework, I've never been able to convince stakeholders to actually adopt one.
Hey I’m a designer and I love UI frameworks. Why design and build something from scratch if someone’s already doing it for you?
Unless there’s a very specific business case that requires a custom UI it’s not worth the hassle. I want to be delivering value for the business and for users, not maintaining a UI library.
One place I worked at had built an entire responsive CSS framework, which was hard to use and took a lot of maintenance. I threw it all out for Bootstrap (as was the style at the time). Some of the senior devs were upset I’d killed their baby, but everyone else was able to move so much faster.
The last time I heard this from a designer, the designs we got constantly violated the UI framework in ways that required deep customization.
I'd love to have a designer that started with a style guide and then actually stuck with it. Writing CSS isn't hard, and sticking with a known set of rules makes it even easier. But then this one component needs a slightly different font size that doesn't match up to any of the established typography rules, and this other spot needs unique padding, and and and I end up having to waste so much time looking for these little surprises.
Been there! I see this as a solo dev or small startup tool, great for building 0-1 ideas faster (which is what I use it for). Unless they’re working on greenfield apps, established teams probably aren’t the ideal fit.
Do you not use Tailwind? What is being wrapped? Designed and built this all as a Ruby gem, you can one-click install if you want to build prototypes with Rails even faster. I suppose you're not the target customer, but thanks for chiming in.
I'm not saying this product is good or bad, because I have no idea, but this is priced too low for it's claimed value prop, not too high. 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.
I'm not saying the product is unserious; just that developers are generally unserious about pricing.
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.
You’re overlooking Hotwire, PWA as a first-class concept, and Hotwire Native — the easiest way to take a functioning web app and migrate it to native mobile apps on both iOS and Android. I’d encourage you to take a fresh look at the new Rails technologies introduced in Rails 7 and Rails 8. You may find that the current Rails stack is the best fit for most, though not all, cloud applications that need a web client along with iOS and Android clients.
I might be missing something, but was this project started in 2016? I'm not sure what line in the sand you're drawing. That was some minima for developers "knowing UI actually matters" I presume?
In general, I like it for the speed. I can build an MVP in less than a weekend using Rails, Rails UI, and some AI for some one-shot copy and random repetitive stuff.
Under the hood, I like the Rails conventions and Ruby's beauty.
It looks good, but I'll be honest, it's hard for me to consider $299/$799 if I can buy a beautiful theme off of somewhere like ThemeForest for $20 or $30 and toss it into an LLM to get the files parsed into components and templates.
That's fair. Probably not a good fit for you then. I wanted to keep the human element alive where I could with this project and I know AI will likely take all our jobs, so be it. It's solving a need for me when it comes to building ideas quickly so I figured maybe others would benefit. I'm a product designer by day and love building front-ends so it's also a passion project.
Sad for the creators of the world. I enjoy the benefits of AI, but I hate if for creative individuals like @justalever.
We (developers) were all sold a promise years ago of technology/software being our future. That's changing rapidly, and there's no going back.
You don’t even need to do that anymore. It’s capable of visiting those sites and just copying the components look and feel. Try it. Ask it to make a template based on a theme you found and show it the link to the demo and BaM! You got something similar.
It's really weird to me how people on this site used to have a much bigger problem with ripping off other people's designs and work, but the minute it became turnkey it was like, "sorry art nerd guess you starve now roll coal".
I didn’t make it this way. It’s not my fault.
This definitely does fill a gap that Rails has. I love using it but man I can't make a nice looking front end to save my life. We've used Tailwind UI a ton but thats kind of a foot gun because you end up slightly tweaking classes all over the place if you're not disciplined.
I've fiddled with Open Props [0] a bit lately, seems like a nice middle ground! Colours/fonts/spacing/etc that look nice together are there, but it's still up to you to use them. (And you're still writing CSS, so might be a deal breaker if that's the part of tailwind you like... but CSS is rather nice nowadays.)
[0] https://open-props.style/
I used this about a year ago when I went through a short Rails phase. I was a bit surprised not to see more Rails-specific UI libraries considering how batteries-included the rest of the framework is, and at the time I didn't really 'get' tailwind. I'm not in a Rails phase anymore, but nice work on the library!
Hey, thanks for giving it a shot! Agree on the UI front. It seems to be the most "unconventional" thing about the framework. Always struck me as odd, but I suppose it makes sense given how an app needs to adapt to a brand, audience, and market.
I've launched 3 Rails SaaS products in the last 6 months, all profitable. In the world of LLMs things like this feel less valuable. I can kick off a Claude Code prompt and in 1 hour have a decent design system with Rails components.
Things like this likely need to be AI-first moving forward. This feels built for humans.
That's fair. I think there's a future where some folks won't want AI to generate all the things. I replied to another comment before but this was very little AI minus some architecture direction of the underlying ruby gem.
Personally, if I feel like you vibe coded your SaaS I’m probably not gonna pay for it. You can obviously tell when a project is vibe coded just based on the way it looks, the weird bugs you see and the poor documentation.
There’s definitely a market for good looking UI that actually works and stands out from the vibe coded junk. Artisanal corn fed UI I guess.
Same here. This was human driven UI. I used AI sparingly for mostly architecture decisions on the gem. Otherwise all by hand. I'm a product designer by trade.
Any chance to reach out to you? I'd like to ask you some questions about those SaaS (not in a bad way, just trying to learn)
Maybe they used AI to make this ? But really though I hope they didn't and did some of designing themselves... I'm worried we are approaching a world where we never get new human designs just regurgitated designs from pre 2025.
I used AI sparingly actually. Mostly just some help for Ruby gem architecture and how to approach swapping themes on the fly otherwise all me. I'm a product designer by day so this stuff I do constantly.
I came here to say: Is someone going to tell him? Glad I’m not the only one to be like “Wait.. I can do this with an agent in no time”.
In fact, armed with Context7, Claude could recreate this whole business model in a day.
Definitely aware. I built it to scratch my own itch to be honest. I'm going the non AI route with it. Lotta slop out there. I'm sure it will improve but I'm fine with this being a side gig.
Good to see work in non-AI world and for Rails!
I would make it clear in the landing page that the components are for demonstration purposes by adding a title like "For example" before them.
The above the fold looks a bit packed right now. I would leave the login box out until user presses top right as it's for retentive users only.
Agreed - particularly because there is an example of a login box and the screenshot of that is far more prominent than the rest of the design.
I don't think the demo should overpower the landing page.
And then it goes straight into themes. If I'm a Rails developer I'm not looking at theming, I'm looking for a conventional UI system that fits into Rails - stimulus, Hotwire, all that.
As far as I know, this site so far is just a bunch of specialised scaffolds for certain use-cases, but Rails itself has been capable of that the entire time.
Good feedback! This is a common misconception about themes. Rails UI is more of a hybrid as it offers UI components plus optional pages that build out a theme using those components.
You can either take the pages and tweak them for your own use case, or just use the UI components and skip the theme entirely. If you get a chance, try the free Ruby gem to see what I mean.
Thanks for chiming in!
The login box is maybe confusing or maybe I'm misunderstanding you, it's actually UI for a login box, not actually where you login. I agree this area could be tightened up.
Did a quick search and no-one has flagged a11y/colour/contrast but the animating effect for the brand colour often had a colour contrast around the 1.0 range.
Yeah pretty much didn't care about it for the sake of effect. That's a big no no I know. The website isn't really the focus as the goods in the ruby gem are more of the focus. Consider railsui.com a billboard if you will.
If you’re showing off a UI framework, I shouldn’t be accidentally scrolling left and right on the page on mobile / my iPhone. Couldn’t be bothered to scroll down the page to look at components while accidentally activating horizontal scrolling.
Will get this fixed, thanks!
It happens on Firefox on Android as well
Thanks
This is interesting to me as someone who worked with Rails a good deal back in the day and has interest in picking it back up.
Any chance of some themes that bring in a little dimension? Doesn't have to be early 2010s Bootstrap or anything but some subtle, crisp drop shadows and gentle gradients would be welcome.
Additionally, is unused Tailwind CSS shaken out or does it all come along for the ride?
Yes, it's on my radar to add more unique designs to the mix. Less typical, if that makes sense. For now, it's mostly a huge head start if you're building quickly.
And yes, unused Tailwind CSS is automatically extracted when it's built. For Rails, we use the tailwindcss-rails gem as a dependency for Rails UI, which JustWorks™.
Waiting for something similar but without Tailwind and with native elements.
Started this whole thing off thinking I'd use Bootstrap, Tailwind, and other frameworks but it quickly became way to complex. Tailwind won the battle.
Broken in Safari on iphone. For example:
- table background moves left when table is scrolled horizontally
- actions in table and dropdown do nothing on tap
- text on buttons is selectable (really?)
Gotta love Safari. Thanks for spotting.
i don't get these types of products anymore. i think they're useful in their own way, but i can literally create styles with claude/gemini in a heartbeat and not have to pay some insane fee.
Fair enough. Yes, AI can one-shot a lot now, but I sort of think human-coded stuff has its place. Having done both, I'm most often cleaning up the AI UI that did a piss poor job. I'm sure it can improve in time, though. I built this to scratch my own itch as I'm doing a lot of 0-1 development on ideas.
Time (and money) will tell.
My guess is there's a lot of shops that don't want to mess with prompting AI to get to something clean and usable, and would rather just save money and pay the fee.
I think you missed a trick not naming it Railwind UI.
maybe I'm just dumb but a lot of these elements don't seem to work? the "..." buttons don't open any flyout, the dropdown doesn't open up...
otherwise looks cool though
Hey! A lot of the UI on the theme preview site and on railsui.com isn’t fully functional. It’s mostly there to show the design and layout of the components, not the underlying logic. The railsui gem itself has more complete, working components and pages.
I wish I could use this – unfortunately UI frameworks are a political problem at every company I've worked at. The designers feel undermined or threatened by it, and product owners want to dictate design. Despite the massive productivity benefits of a UI framework, I've never been able to convince stakeholders to actually adopt one.
Hey I’m a designer and I love UI frameworks. Why design and build something from scratch if someone’s already doing it for you?
Unless there’s a very specific business case that requires a custom UI it’s not worth the hassle. I want to be delivering value for the business and for users, not maintaining a UI library.
One place I worked at had built an entire responsive CSS framework, which was hard to use and took a lot of maintenance. I threw it all out for Bootstrap (as was the style at the time). Some of the senior devs were upset I’d killed their baby, but everyone else was able to move so much faster.
The last time I heard this from a designer, the designs we got constantly violated the UI framework in ways that required deep customization.
I'd love to have a designer that started with a style guide and then actually stuck with it. Writing CSS isn't hard, and sticking with a known set of rules makes it even easier. But then this one component needs a slightly different font size that doesn't match up to any of the established typography rules, and this other spot needs unique padding, and and and I end up having to waste so much time looking for these little surprises.
Been there! I see this as a solo dev or small startup tool, great for building 0-1 ideas faster (which is what I use it for). Unless they’re working on greenfield apps, established teams probably aren’t the ideal fit.
is this daisy for rails?
Felt more like a Tailwind UI (https://tailwindcss.com/plus) to me
I have hardware acceleration disabled in Firefox and my 5800X spins up trying to render the background wave. At least that's a known choice I made.
Oh damn, haha. Sorry if it cooks your machine.
Is this another Tailwind wrapper? Yes, it is.
Do you not use Tailwind? What is being wrapped? Designed and built this all as a Ruby gem, you can one-click install if you want to build prototypes with Rails even faster. I suppose you're not the target customer, but thanks for chiming in.
I think their comparison page does a good job of breaking down the differences (vs Tailwind UI that is) https://railsui.com/compare/tailwind-ui-vs-rails-ui
But this one costs $799 a year.
Pricing page if anyone else is curious: https://railsui.com/pricing
"Solo" plan is $299/year (1 seat), "Team" plan is $799/year (30 seats), larger plans are "inquire now".
I'm not saying this product is good or bad, because I have no idea, but this is priced too low for it's claimed value prop, not too high. 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.
I'm not saying the product is unserious; just that developers are generally unserious about pricing.
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.
God grant me the confidence of whoever vibe coded this
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.
Thanks for noticing. It's all hand-made with a bit of AI to talk me off ledges on the gem structure/architecture front.
Yes, for a 30-seat license.
What does this even mean? Tailwind isn't like Bootstrap; it's a way of structuring styles, not a design language of its own.
I'm generally in favor of "Show HN" posts that are products, but this post just seems like blatant advertising.
There's an open source Ruby gem you can use at will. https://github.com/getrailsui/railsui
Rails is best as an API only, that's where it shines for me like no other tool.
You’re overlooking Hotwire, PWA as a first-class concept, and Hotwire Native — the easiest way to take a functioning web app and migrate it to native mobile apps on both iOS and Android. I’d encourage you to take a fresh look at the new Rails technologies introduced in Rails 7 and Rails 8. You may find that the current Rails stack is the best fit for most, though not all, cloud applications that need a web client along with iOS and Android clients.
ugh this looks dated even by 2016 standards
when will developers learn UI actually matters
bootstrap was a mistake, and lowered the bar for everyone
I might be missing something, but was this project started in 2016? I'm not sure what line in the sand you're drawing. That was some minima for developers "knowing UI actually matters" I presume?
This you? https://flow-control.dev/
I would advise refraining from posting sick owns like this in your own Show HN threads.
i wish :(
im always surprised that Rails is still relevant
i havent used it since 2006 opting for php and django
i might give it another shot, any reason you like this more than django or other frameworks
Please check out my response to another comment on this thread as so much has changed especially recently. https://news.ycombinator.com/item?id=46712477
In general, I like it for the speed. I can build an MVP in less than a weekend using Rails, Rails UI, and some AI for some one-shot copy and random repetitive stuff.
Under the hood, I like the Rails conventions and Ruby's beauty.
I guess it depends if you are used to Rails.
Personally, I don't see the point in ever touching rails since bunjs gives me everything I need while being faster and typescript compatible.
Ruby does look pretty, but that's it.
Is there any benefit that would justify giving it a try if you already use typescript?