Feature complete? Not likely
Releasing the first version of a product should never be feature complete. That is to say you probably shouldn’t do every feature you want to do right from the start. Things that seem important in the planning stages might become altogether worthless to the users, while they spot huge holes that you’ve left unfilled elsewhere. In the end it’s all about getting done the core of your project — what people are coming there to see. If the forgot password form process ends up being a little odd, or some graphic seems a bit off; but users are still able to do what you wanted them to then you have yourself a great success. The rest of the details can easily be hammered out, and even better organized with user feedback.
For ArcadeFly it’s obvious what the core features of the project are. Finding arcades to play games at. There are a few features that aren’t going to make it into launch, but nothing I’d call a showstopper. There won’t be a friends system, a comment system or a messaging system right out of the gate. For starters it’ll be all about finding the arcades. Then as people join up, I’ll see where resources are needed and probably work on adding more ways of users to communicate. This really makes sense anyways, after all how can you message people or add friends until there’s a user base out there. The lack of commenting I do miss, but it at least it means deferring those questions like “How do I weed out spam?” and “Who deletes spam?”. Doing more work now could very well lead me to investing even more time down a path I don’t want to go. Best to keep it simple while you can.