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.