Knaqq was my project for the ProductHunt Makers Festival. I have decided to launch it as a regular ProductHunt product. It didn't get as much traction as I thought it would. Why is that? Knaqq is the best thing that happened since sliced bread! Well I have a few theories about why this launch wasn't as successful

Lack of Research (once again πŸ€¦πŸ½β€β™‚οΈ)

I did not do enough research into the problem I was trying to solve. Even though the mini book format is popular on social media, it doesn't necessarily mean that people will jump on the app immediately. I don't know if people want it and I don't know if creators want a platform dedicated only to post this type of content.

TODO: Do more interviews with creators on Instagram

Didn't build an audience

From what I see on ProductHunt, IndieHackers and other communities most founders build an audience and have beta testers. Most of the time some of the testers share the product, and give testimonials which helps with marketing. I don't seem to understand how to build that initial user base yet.

Conclusion: I didn't solve a problem

As a developer I tend to get caught in the illusion that being able to build something means that I imperatively have to build it - especially now that I am able to do full-stack web development.

This product launch makes me realize that I want to focus on solving problems instead of building every idea I get

Focusing on a problem would give me more direction and help with building a small user base early on. Solving a problem however brings another issue: finding a problem to solve. According to the people I talked to on IndieHackers there are multiple ways to find problems to solve:

  1. You experience it yourself
  2. You spot it from working in/with a particular industry
  3. You do directed research to find it

1 and 2 will be very hard for me since I don't have a lot of experience like most founders and 3 will require learning how to do redirected research (whatever what that means πŸ˜…)


All together Knaqq wasn't a total failure. It was my first project using ASP.NET Core and Angular, I have learned a lot building it. I also built something for a competition and even though I might not win I was able to set a time frame and build something in that time frame. I also believe that this format can be useful for people so I will keep looking for content to add and share as much as I can.

Before building anything else I need to do the following:

  1. Find an industry that I understand
  2. Look for pain points in that industry (the more people have the problem Β the better)
  3. Figure out how people are solving the problem and find if there I can differentiate myself from the existing competition