4 ms·
I know the conventional wisdom here would be to release early. But beware the distraction that can be -- you suddenly need to find some extra time to worry abo
by aquark 16y ago
I know the conventional wisdom here would be to release early. But beware the distraction that can be -- you suddenly need to find some extra time to worry about keeping the server up, responding to feedback, etc.
If you really feel there is a killer feature that sets this apart from a 'me too' site, then I would push to implement a minimal version of that and release with it in place.
Of course if you have not validated the killer feature in any way then maybe it is worth the time to mock it up and try and get feedback. Perhaps a simple landing page without any site around it would serve that purpose and not distract people with the basic features.
- codeslush 16y agoYou have just provided me something super valuable. Thank you. I knew I needed a landing page, but I was thinking about just finishing things up and not doing a landing page. Based on the feedback I've received here, I think I will do the following: 1. Create a landing page that highlights the main features - including the killer feature - and see what happens with feedback. This will allow me to really focus on my message as well; and make sure it's clear and concise. 2. Will reach out to a small group of people here on HN and get it in their hands for some feedback - w/o the main feature, but enough functionality that they can gauge interest and start providing feedback and/or features. The splash page should definitely validate the feature -- and it totally makes sense to get that validation before I implement it. I'm pretty confident, but it's based on my own observations and needs - and something that's been biting at me for a while. I'm very excited!!!