4 ms·
Really? I think the whole point is to launch as early as possible. "Release early, release often" Plus you want to get up and running, get some users, and sta
by goodkarma 18y ago
Really?
I think the whole point is to launch as early as possible. "Release early, release often"
Plus you want to get up and running, get some users, and start building momentum (which comes from people using it, talking about it, giving you feedback, etc.)
I recommend building the app for yourself. You will know what features need to be done first.
- AndrewWarner 18y agoAlex, I'd love to hear how you did that for easytweets.com. Looks like you have a broad collection of features. How'd you decide which were core and needed to be put in before launching and which could wait?
- goodkarma 18y agoI made the app for myself. I wrote the first code a few days before flying to Startup School last year. I wanted to be able to tweet things when I was traveling. Initially, all it did was schedule tweets. That was the feature I wanted most. Over time, as I wanted it to do more, I wrote more code. There are tons more features we will add - and a lot more that I'm sure we will add that we don't even know about yet. I am trying to constantly keep my ear to the ground and listen to my users and influential folks in the search marketing industry and trying to prioritize what needs to be done based on feedback and my own daily use of the app. It's kind of the whole premise of what PG says to do - launch early, and listen to your users. Many startups change their whole model after they launch. We now offer many features I would have never guessed when we launched the app last year.