Live data from Hacker News

My app failed: lessons learned

rithm.app

131–140 of 177 posts

Re: My app failed: lessons learned

#131
post #130

Regarding lesson 4 (Distribution), the author links to a tweet by Justin Kan saying "First time founders are obsessed with products. Second time founders are obsessed with distribution". Justin Kan posted[0] today a video of himself criticizing that very tweet, saying that it didn't age well and he now believes product is 99% of the work, and the reason that many unicorns are founded by first-time founders is they do…

A good enough product with great distribution can earn you a fantastic income if you bootstrap.

Re: My app failed: lessons learned

#132
post #122
post #105

Earlier quoted context omitted.

What does this mean?

it means a bad market will make even a good product unsuccesful, and a good market will make even a mediocre product successful. the quality of the market wins out over the quality of the product.

Does this mean the market works by manipulating consumers?

Re: My app failed: lessons learned

#133
post #59

> The app landed as the #4 product of the day on ProductHunt, had some good initial traction which proceeded to fall off a cliff. This is why you don't post on ProductHunt. Your target market isn't there. Its nothing more than an ego trip for so many founders.

I've posted on ProductHunt as well and so many of the upvotes I get and comments that I get are clearly spambots.

> so many of the upvotes I get and comments that I get are clearly spambots.

Is there any data on this? I'd be interested to see what % of real users they have.

Many times I've visited ProductHunt there's a top 4 app that doesn't seem useful at all that has tons of generic comments like "Great work!", "Can't wait to see what you do next!", "So useful!" (common on Twitter too).

Guessing you could get bots to vote + comment occasionally to build up their reputation and then use or sell your bot army to manipulate the votes for specific product launches later?

Re: My app failed: lessons learned

#134
post #122

Earlier quoted context omitted.

it means a bad market will make even a good product unsuccesful, and a good market will make even a mediocre product successful. the quality of the market wins out over the quality of the product.

Does this mean the market works by manipulating consumers?

The market _is_ consumers.

Re: My app failed: lessons learned

#135

Earlier quoted context omitted.

At least for this particular flavor of app, building an Android version is an optimization that should be made once the product has been proven successful. Until that happens, it would be a huge waste of time and money for the developer to build an Android version, since it too would fail as a product, just like the iOS version. Multiplying 0 by 2 is still 0. The situation might be different for an app whose success…

Why not build something like this cross-platform? The functionality sounds simple enough that you don't really need a native app for each platform.

It seems like it would be simple enough, but it's death by a thousand cuts. Supporting Android means having to keep track of even more screen sizes, OS versions, updates, app store releases and so on. It just adds on more and more. For one developer who is trying to prove out an idea, the work to support the app on multiple platforms just eats up your time and focus when you really should be focusing on features and adjusting what the product is as you get more info from your existing customers.

There are of course frameworks out there to help you build one codebase for multiple platforms, but if you go down that route, if you aren't familiar with the framework, you have to learn it. There are going to be quirks in them that you're not aware of. Maybe framework version X only works with iOS version Y and Android version Z. It just goes on and on. Frameworks aren't perfect either, and things don't work exactly the same across platforms even with the framework.

Re: My app failed: lessons learned

#136
post #59

Earlier quoted context omitted.

I've posted on ProductHunt as well and so many of the upvotes I get and comments that I get are clearly spambots.

> so many of the upvotes I get and comments that I get are clearly spambots. Is there any data on this? I'd be interested to see what % of real users they have. Many times I've visited ProductHunt there's a top 4 app that doesn't seem useful at all that has tons of generic comments like "Great work!", "Can't wait to see what you do next!", "So useful!" (common on Twitter too). Guessing you could get bots to vote + co…

I don't know if there's data, but I've seen other people posting about on Indie Hackers. I started noticing something was up when I saw the same generic comments you mentioned on my post as other people's posts.

Another thing that's interesting is after you post on Product Hunt, you may get emails from third parties offering services to boost your upvotes.

Re: My app failed: lessons learned

#137
post #15

Good lessons. But so many common mistakes To summarize: 1) Build something people really need, not a nice-to-have 2) Keeping customers is more important than just acquiring them 3) If you're not keeping your customers that means they don't want or need what you have 4) Changing people's behavior is really hard. Unless you have a significant amount of marketing budget, don't try to change people 5) "Distribution" is k…

8.In hindsight, it's easy to give advice to others on their flaws than making it a reality on your own. Making a list really sells it to people. 9.Stop making products, start writing personal development/marketing books that contain things that seem obvious in your head but you've never really tried it yourself. 10. Make your fluff seem as authentic as you can

> Be kind. Don't be snarky. Have curious conversation; don't cross-examine. Please don't fulminate. Please don't sneer, including at the rest of the community.

> Please respond to the strongest plausible interpretation of what someone says, not a weaker one that's easier to criticize. Assume good faith.

https://news.ycombinator.com/newsguidelines.html

Re: My app failed: lessons learned

#139
post #58

Slightly OT: I built myself a journaling app that sends one email every day to remind me to write about that day; I respond to that email and the response gets stored in a db as an entry for that day. The system doesn't try to be clever in any way, it just sends and receives emails; it's proven quite effective. It's been running for about two years now and there are only a couple of days missing, if that. It's very i…

Also OT: I built something very similar, but with text messages and asking for a positive thing that happened during the day rather than a journal entry (forcing myself to look for positive things in a day helped snap me out of a spiral toward depression in the early days of lockdowns). I spent a weekend getting it to the point where it was good enough to share with friends and family, and about a dozen of them signe…

do you mind explaining your stack / tech a bit? would love to whip up something similar for a pet project

Re: My app failed: lessons learned

#140
post #58

Slightly OT: I built myself a journaling app that sends one email every day to remind me to write about that day; I respond to that email and the response gets stored in a db as an entry for that day. The system doesn't try to be clever in any way, it just sends and receives emails; it's proven quite effective. It's been running for about two years now and there are only a couple of days missing, if that. It's very i…

do you mind explaining your stack / tech a bit? would love to whip up something similar for a pet project
Post reply on HN