Why I Started Building My Own Product as a Programmer
I'm a programmer building SmartConvert from scratch. This is the story of why I started, what I'm learning, and what happens when you try to build a product on your own.
- #Indie Development
- #Building in Public
- #SmartConvert
- #Solo Developer
I’m a Programmer
For most of my career, I’ve been doing one thing:
Writing code.
Apps, APIs, bugs, releases, maintenance, changing requirements...
I’ve been doing all of that for years.
But recently, I started having a stronger and stronger feeling:
I want to build a product of my own.
Not something I’m building for someone else.
And not a project that ends once a requirement is finished.
I wanted to start from zero, take an idea, build it, launch it, find users, and eventually see whether it could actually survive.
So I started building SmartConvert.
It’s an online tools website focused mainly on file, PDF, and developer tools.
It’s not some groundbreaking product.
In fact, it doesn’t have many users every day right now.
But that’s exactly why I want to document the journey.
Because I’m genuinely curious:
Can an ordinary programmer, working alone, use today’s AI tools and low-cost cloud services to build a real product that people actually use?
What Happens Before the Success Story?
I’ve read plenty of stories about successful indie developers.
Someone makes thousands of dollars a month.
A product gets tens of thousands of users within a few months.
A solo founder builds a SaaS business and reaches impressive annual revenue.
Those stories are inspiring.
But I’m more interested in another question:
What actually happened before the success?
What happened when the product first launched and nobody used it?
What do you do when you only have a few dozen visitors a day?
Does SEO actually work?
Should you spend money on ads?
Where does the first dollar come from?
And once a programmer starts building a product, how many problems appear that have nothing to do with writing code?
Those are the things I want to find out for myself.
So I Decided to Document the Process
I’m not going to write about "success strategies."
I don’t have any success story to share yet.
Instead, I want to document what actually happens along the way:
What I built.
Why I built it.
How much I spent.
How many users showed up.
What I got wrong.
And what happened in the end.
For example, I’ll be documenting the growth of SmartConvert as I continue building it.
I’ll also write about how I use AI coding tools to develop products, and what it’s actually like to work with services such as Cloudflare, AI platforms, browser extensions, and other developer tools.
If I eventually make money from it, I’ll write about that too.
And if it fails, I’ll write about that as well.
Because I think that for someone who is seriously thinking about building a product, a real story about failure can be more useful than a beautifully packaged success story.
This Is Where It Starts
So this is where the blog begins.
I’m a programmer.
And now I’m trying to build a product on my own.
Welcome to The Indie Development Log.