Features and Situation
Okay, back to the blog. The last post was simply an attempt to get something out quick-like, and in that sense it was successful.
As I said before, the Recurse launch went fantastically well, but it suffered from a few things. Things I wish I’d have thought about beforehand, but have no means of correcting now that it’s happened.
- I wish I’d asked users upon sign-up if sending them an emails would be okay. As it is now, I’m going to end up sending a preliminary email to ask if sending more emails would be okay. Not the end of the world, but not great.
- A big button saying “Leave Feedback” or something along those lines would have been infinitely useful. I’ve used them before with app launches (Togethr), and people use them a ton. I can’t believe I blanked on adding one to Recurse and it’s the first thing on my list of to-do’s.
I thought that list was going to be longer, so it seems as though things are in good shape. Regardless, I think the major thing Recurse is suffering from is something I’ll call a “readiness” factor.
When a beta users stumbles onto the site they don’t necessarily have the files they need to upload on hand. They may not have any client work right that minute, and they may forget to return to the site when they do get the work. Also consider that webdesigners aren’t going to be super keen to beta test Recurse with their clients while trying come across as professional (there may be bugs, etc).
Aside from that, there are a list of featured that I need to implement and things should keep rolling along. I’m going to figure out this feature list and then update the blog as I implement them.
