1.9K
upvotes
246
comments
5
insights
5
tags
This launch was successful because it addressed a core pain point for indie makers: the difficulty of achieving consistent growth through frequent launches. The author's relatable narrative, combined with direct questions and a willingness to share lessons learned, fostered significant community engagement and discussion.
Relatability of the maker's journey: The post taps into a common struggle of indie makers (launching many products with limited success).
Honest reflection and vulnerability: The author shares personal learnings from a large number of launches, admitting to chasing virality.
Thought-provoking questions: The post encourages community participation by posing direct questions about strategy and experience.
Empirical evidence (even if limited): The mention of 'Refgrow' showing slow but steady growth provides a concrete example supporting the author's new philosophy.
High engagement on the subreddit: The substantial upvotes and comments indicate strong interest and resonance within the r/SideProject community.
I do all my projects on Node.js, PostgreSQL, EJS, Bootstrap 5. I used to use VS code, now Cursor. I have never used any ready-made templates. I just took my previous product and used it as a template for a new product.
Alex-growFirst of all, that is an impressive list! To answer your question: I don't think there are easy, black and white answers. Sometimes it makes sense to keep building things, launch, see whether it gets any action and if not, move on and try something else. Until something sticks and makes sense to invest more into. But also, sometimes it makes sense to keep building a single product and invest into it until it succeeds (or you run out of time and money). There are examples of both strategies working. Perhaps it's more of a personality issue. If you have problems in focusing to a single product and you always want to build something new and exciting, then perhaps that is a better strategy for you. But if you prefer to sit down and really polish your product and work on it, maybe that kind of "slow growth" is for you. I have been building products and releasing them since 1999 and I have done both styles of development. As with everything, they both have their fair share of pros and cons. And just like you said, it's basically impossible to guess which products go viral. One thing that people who build products rarely mention is luck. I think there is a fair amount of luck involved in every product that one builds. For example, you might get lucky and some person with influence might share your thing and even recommend it. Such things can really help you out. But another thing that I have also noticed is that the harder one works, the more good luck one tends to have. Hard work doesn't guarantee success by any means. But laziness and low quality almost always guarantee failure.
JouniFlemmingWhat a surprise, consistent effort beats chasing trends…
CtrlShiftRoI don't understand why people call websites or apps a product. Wouldn't that be a service? Okay, I know banks, insurance companies also call their stuff product, but maybe I don't even agree with that either :D It just feels weird.
TheBlacktomBecause after you finish building the website or app, it does things almost automatically. Services should be served actively. Products are passive. The website or app gives the service not us. For us it's passive.
the_professor000Tags
Post details