What started out as a Vibe Coding project turned into a full-on side project that I’ve decided to build in public.

So, what is Wizzle? At its core, Wizzle is a straightforward wishlist sharing web app designed to take the headache out of gift-giving. No more awkward duplicates or guessing games about what your friends and family really want.

Wizzle was born from a real-life holiday fail: last Christmas, my sister-in-law and I both bought my wife the exact same pair of in-ear earphones. She swears by her system, a shared Google spreadsheet with tickboxes, that keeps everyone in sync.

As a software builder, I naturally started thinking, “There has to be a better way.” And that’s how Wizzle came to be — simple, no fluff, just the easiest way to create and share wishlists with the people who matter most.

Why am I building in public?

I’m building in public because I’m genuinely excited about this project and want to see it grow, no matter how messy the journey gets. Sharing what I’m working on keeps me honest and motivated, especially since working alone can sometimes feel like shouting into the void.

Even though there’s no community around Wizzle yet, I’m eager to hear what you think, get your feedback, and make this app something we all want to use.

I won’t sugarcoat it, putting unfinished work out there feels a little scary, and I’m definitely bracing for some criticism. But I believe that showing the real, imperfect process is the best way to learn and improve.

I’ll be sharing updates here, and posting on Reddit and LinkedIn so jump in anytime, leave a comment, ask questions, or just follow along for the ride.

So what tech stack am I using?

Wizzle is built with Ruby on Rails, my trusty sidekick for crafting web apps quickly and cleanly. The interface uses simple .html.erb view files paired with custom CSS, keeping things straightforward and easy to use. No fancy frontend framework, just what’s needed to get the job done.

For storing data, I’m using Turso, which runs on SQLite. It’s lightweight, speedy, and just the right fit for a project that’s just finding its feet.

At the moment, Wizzle doesn’t lean on any third-party services or APIs. I’m all about keeping it simple so I can focus on building the core features that really matter and avoiding unnecessary distractions.

Why Ruby on Rails? Honestly, it’s my favorite toolkit. I’m a Ruby dev by trade, and I love how elegant and productive Rails is. Sticking with what I know lets me move faster and have more fun building something I’m passionate about.

The not-so-fun part? Hosting and deployment. That’s been a bit of a learning curve since it’s not usually part of my daily work. But hey, that’s part of the adventure, and I’m here to figure it out and share every step of the way.

What's next for Wizzle?

I’m just getting started, and there’s a lot cooking behind the scenes. One of the next big things I’m excited about is allowing users to collaborate on wishlists, making it even easier to plan gifts with your close friends and family.

There’s also a feature I’m really passionate about called communities. I won’t spoil too much just yet, but it’s something that could change how people connect and share wishes in a whole new way. Stay tuned!

Down the line, I’m planning to build a browser extension to make adding items to your wishlist smoother and faster.

On the practical side, I’m focused on improving testing to make sure Wizzle runs smoothly as more users come on board.

Speaking of users — growing the Wizzle family is a big milestone I’m aiming for.

I really want to hear from you, that’s why I’m adding a “Request a Feature” section to the site (coming soon). Got an idea or something you’d love to see? Drop it in, and I’ll be all ears.

No flashy launches here — updates will quietly roll out as soon as they’re ready. Just steady progress, and I’m thrilled to have you along for every step of the journey.