timqian

My one-year experience as an indie hacker

2020-05-18

About one year ago, I quit my job and started my career as an indie hacker. My goal was to reach $1000 monthly revenue in one year. The year soon passed, unfortunately, but not surprisingly, I failed. But as a summary of this journey, I would like to share some data and thoughts here with you.

Projects I made

Product Status Github Stars Registered Users Downloads
Feeds.Pub 🌱 haven’t open sourced yet 1534 N/A
Resumd 🌱 331 N/A N/A
Chinese Independent Blogs 🌱 4.6k N/A N/A
Repo Analytics 🌱 104 250 N/A
chart.xkcd 🌱 6.2k N/A 100k+
wewe 🌱 317 133 N/A
Help wanted đź’€ N/A N/A N/A
Open Source Jobs 🌱 1.1k 153 N/A
Tomato Pie 🌱 198 1k N/A
cloudquery 🌱 2.1k N/A N/A
cloudfetch đź’€ N/A N/A N/A
Star History 🌱 1.8k N/A N/A

Monthly revenue

$14 per month from Patreon

$57 per month from Afdian (Thanks to immux.com)

About $18 per month from Star History

What I did wrong

  1. Not focusing enough: In 12 months, I built 11 different projects. I should have focused on one project earlier.

  2. I am targeting the global market but wrote my blog only in Chinese.

What I did right

  1. I built a lot of different things: building is the best way to learn. Although I failed to build a product with enough MRR, the process made me a better builder. And it gave me some sense about products. Whether a product can attract people’s eyes when it launches? Whether a product can “only” attract people when it launches, but people will not actually use it? Whether a product may not gain a successful launch but the search engine, network effect might make it worthwhile to try.

  2. Recording things down (in Chinese): so I can reuse what works and prevent mistakes from happening twice. My blog brought me some readers and initial users. I made some amazing friends thanks to the blogs. One product might not live longer than some decades, but the experiences and thoughts might have the opportunity to influence people for a longer time.

What’s next

  • I will focus mainly on Feeds.Pub to make it as good as I can. But continue building side projects (with less focus).
  • I started this English blog and will continue blogging.
  • I am starting to look for freelance work and opportunities in startups. If you are looking for someone to build your app, you are very welcome to contact me.

Should you consider being an indie hacker?

Building apps is becoming more and more easy

Node.js, React, React Native, Electron, Flutter, Bootstrap, Tailwind CSS… tools to help build apps occur rapidly. Although some developers are complaining about too many things to learn and too many choices to choose from. But it is important to note that these new tools are built to facilitate software engineering. You may have already noticed, there are lots of young people, even in primary school, who got their own personal website and side projects. This was hard to imagine 10 years ago.

Building successful apps is becoming more and more hard

Building apps is becoming easier and easier. Hundreds of apps are shipped every day. But the population on this globe is limited, as is their attention. It is predestined that most apps get no traction.

So, if you are not good enough in any aspect of luck, programming, creativity, patience, or design, it might be hard to earn a living as an indie hacker.

It is the best of times: anyone can create things with low cost. It is the worst of times: anyone can create things with low cost.

So, should you consider being an indie hacker?

If you’ve got enough savings to sustain yourself for several years and are eager to try, it will be a fun journey. Being an indie hacker is good practice in many aspects, and it won’t be very hard for you to find a new job if you fail.

If you are just bored of “working for others,” you might be disappointed. As when you start building apps yourself, you will soon find there isn’t much difference between indie hacking or working for others. Most times, you will be doing the things “you must do.” A better choice is to join a good team, learn to build a successful product.

Discuss on Twitter | Edit on GitHub