justalever

I hear you. I'd say the value prop is drop-in integration and customization with Rails, time-saving design (useful for 0-1 or early-stage ideas for non-design-savvy folks), and fewer headaches compared to adapting other components or themes in the wild into a Rails app.

No matter what you choose, there's work to be done to adapt to each app's use case, branding, copywriting, etc. Rails UI definitely isn't "complete" and is a constant work in progress, hence the subscription model.

Whether that's valuable to you is definitely up to you. Some folks don't want to be beholden to an AI for design and prefer a ready-made human-engineered system to refer back to and evolve as their app does.

I use this project for my own stuff. That's why I originally built it; however, I'm biased and am deeply on the Rails bandwagon. Ultimately, it saves me a bunch of time, which to me is the most valuable thing there is.

I hear you and it's coming up next. I needed/wanted to lay ground work for stuff that's easier to tweak to match your own branding. Many Rails apps are similar in niche so I tried to compensate on that front.

Plenty of free options out there. Have at them! There's a completely free version of Rails UI as well. Linked right from the home page hero.

It's like $15 a month annualized. We add new themes and components quarterly. If that's too steep you're not the target customer. Thanks for chiming in.

Pretty much drop in for rails specific UI. Much of it is HTML which could definitely carry over to Django with a little work or one shot conversion with your favorite AI tool of choice.

I heard this from others so will do!

Dang, you're going way back! Thanks for chiming in. It has been a long road :)

What's a better play? Drop the carousel? Open to ideas!

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.

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.

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.

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.

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.

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.

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.

There's an open source Ruby gem you can use at will. https://github.com/getrailsui/railsui

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.

Oh damn, haha. Sorry if it cooks your machine.

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™.

Thanks

Gotta love Safari. Thanks for spotting.

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.

Will get this fixed, thanks!

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.

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.

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.

Thanks for noticing. It's all hand-made with a bit of AI to talk me off ledges on the gem structure/architecture front.

This you? https://flow-control.dev/

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.