I'm Building Software in Public. Here's the Plan.

I've wanted to start making content for a long time. And technically, I already did.

I started creating things, partly because I enjoyed it, but also because I wanted to build momentum. I wanted to get comfortable putting things out there, even if they weren't perfect. I knew that starting was better than waiting until everything was ready.

But there was something I actually wanted to share that I never really got around to.

I wanted to share my journey of building apps. How I come up with ideas, how I decide whether they're worth building, how I design and develop them, and eventually, how I get people to use them. I wanted to document the whole process, not just show the finished product.

The problem is that I kept postponing it.

And the funny thing is, I think I was postponing building apps because I knew I'd eventually want to make content about the process. Somehow, the thing I wanted to do became another reason not to do the thing I wanted to do in the first place.

Why? I'm not entirely sure.

Maybe I convinced myself I needed a better setup, better tools, a proper camera, or whatever else I thought was missing. Maybe those things felt like real obstacles at the time. Or maybe I was just finding excuses to avoid starting before I felt ready.

Honestly, I still don't know.

But I'm tired of waiting.

So, what am I actually going to do?

I want to build and ship apps.

Not just portfolio projects that look good on GitHub, or ideas that stay in my head for months. I want to make things that people can actually use, put them out there, and see what happens.

There's just one problem: I don't have a clear idea of what to build yet.

And honestly, the market feels saturated. There are already thousands of apps doing almost everything you can think of. AI has made building software more accessible, but that also means more people are building and shipping things every day.

It's hard not to wonder whether there's even room for another developer trying to make something.

But I guess I'll never find out by sitting around thinking about it.

So I'll start looking for ideas. I'll explore problems, research existing apps, experiment with different approaches, and try to find something worth building. I'll share what I find, what I decide to pursue, and why.

And when I start building, I'll share that too. The technical decisions, the design process, the things that work, the things that don't, and all the stuff that usually gets left out when someone only shows the final result.

I don't have a perfect roadmap, and I'm not going to pretend I do.

Why I'm doing this

Part of it is that I genuinely want to build apps and see if I can turn them into something people use and pay for.

Part of it is that I've wanted to make content for a long time, and I don't want to keep putting it off until I have the perfect setup or feel like I know exactly what I'm doing.

I also think there's something valuable about documenting the process while it's happening, rather than looking back months later and trying to turn everything into a success story.

I don't know if the apps will make money. I don't know which ideas I'll abandon, which ones I'll actually ship, or whether anyone will care about what I share.

That's kind of the point.

I want to document the process as it is, not just the parts that make me look good.

Let's see where this goes

I don't know exactly what this will turn into. Maybe I'll build something people love. Maybe I'll spend weeks on an idea that goes nowhere. Maybe I'll learn more from an app that fails than one that succeeds.

For now, I just want to start.

No waiting for a better camera. No waiting for the perfect idea. No waiting until I have everything figured out.

I'll figure things out as I go, build what I can, and ship what I make.

Hopefully, I don't postpone it again.