DevChase
From Laravel to Rails: My Check-In App Journey featured image
Dev

From Laravel to Rails: My Check-In App Journey

Published on

I’ve been working on a check-in software for our church. I originally started the project in Laravel which I’ve used for quite a while now but ended up switching over to Rails. Why? A big part of it is cost. I want to avoid monthly fees from platforms like Forge, and Kamal looks like a great option for deploying Rails apps. But I’m still learning Kamal, and I’m still learning Rails.

The switch actually surprised me. I was able to rebuild the app quickly in Rails, and if I’m honest, it already looks and feels better. In just 24 hours, I had a solid MVP up and running. It still needs a proper once-over with a fine-toothed comb to make sure everything is secure and solid, but it’s already promising. I’m also writing more tests this time around and using testing as part of my process has been a game-changer

I’m even considering rebuilding this very website in Rails too, just to immerse myself fully.

Recently, we also started a nonprofit to support ministries and missionaries, and I built that site in Rails as well. It’s called Gospel Impact Solutions. It’s not deployed yet, but it will be soon once I get a little more hands-on experience with Kamal.

Now, I’ll be real: my Rails journey didn’t start out smooth. I spent the last year in Laravel, and I had a lot of Laravel muscle memory that didn’t translate directly. So at first, Rails felt frustrating. But something shifted while I was building this check-in app. Rails is starting make more sense the more I use it. If you’re thinking about diving into Rails, my advice is simple: start building. That’s the fastest way to learn.

Over time, though, I’ve realized something: so much software has become overcomplicated. There’s a feature overload that ends up driving up the price and slowing everything down. Honestly, it’s overwhelming.

Our church is small. We don’t need bloated tools. We need simple, fast, focused solutions that just work. So instead of settling, I’ve decided to build my own tools and build a business around that mission. That is where Straight Wind LLC was born. 

I want to help churches, ministries, and small teams escape the bloat and get back to what matters: clean, purposeful software that serves people well.

So yeah, I’m on a mission now.