Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think that a couple of weeks is far too soon to decide that something is a failure. It's barely even enough time to gather enough data to decide what can be adjusted and improved.

An article that has been posted here before comes to mind:

http://www.sodaware.net/dev/articles/shareware-amateurs-vs-s...

I tend to agree with it. If you're fairly certain there's a market for what you're trying to sell, don't give up on it too soon. Instead, use the information you've gathered to continually refine the product, and execute a marketing plan to try to bring your product to the attention of people who are going to use it. Keep on evaluating, refining, and executing.

In the end, it still might not work out. The danger in failing too quickly, however, is that you'll give up on products that could be quite successful just because they weren't successful right away.



I think that a couple of weeks is far too soon to decide that something is a failure

Agreed. This was originally launched at the start of the year though.

An article that has been posted here before comes to mind

I'm reading through that article now, thanks! :)

The danger in failing too quickly, however, is that you'll give up on products that could be quite successful just because they weren't successful right away.

I agree 100%. All I'm after some form of validation for the idea, not huge success, and so far... well, there' not been a lot ;)


My apologies; I must have misread something in your post.

Validation can be a strange thing. Sometimes you'll make a little change that seems inconsequential, and it will make all the difference. If nothing else, look at it as a fun opportunity to try to find those seemingly tiny differences that end up being huge to potential users.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: