Hacker News Reader

You missed 7 which is try something else. If you are set on this idea then start with 1. Work out what all the issues are first with one site and then think about scaling.

View on HN

It was actually option 6 ;-) thanks for the input. That is our hunch too however I suppose the difficulty has been knowing when to engage: too early and you're just some guys with promises and vapourware, too late and you've got a feature rich app that has missed the boat.

It is for this reason we set ourselves a mini goal of a prototype with cut down features.

My experience is try to couple the development of your app as close as possible to solving the problems of your users. You really need to find someone who can help you find out if the concept is viable or not. The major thing to look for is does your app solve some problem that your paying (future) customers need solved. The only way you are really going to find this out is get at least one involved.

Reply on news.ycombinator.com