MrMatt

Say you've got a new version of your app coming out, but before you release you want to run a beta test to make sure there are no last minute bugs or usability problems.

What tools do you use? Are there any you'd recommend?

So we've finally pushed Purify live, and I would be grateful if I could get some feedback.

It's bug and feature tracker with Github integration that has been built for speed.

This isn't a MVP, we've spent a while beta testing and polishing, so we're considering this version to be the first full-on release. We're waiting on our merchant account to be set up, so until then, there are no paid accounts - just the free one.

Constructive criticism gratefully requested :D

http://purifyapp.com

I've built a site for climbers called Bouldr (http://bouldr.net) - a worldwide, user editable guidebook for climbers.

Recently, I've been toying with the idea of making all of the data that has been submitted to Bouldr open (Creative-Commons) to everyone in the form of a downloadable archive as well as an API.

My thinking is that if I make the data available in a similar way to how Stack Overflow already does, then more climbers will be motivated to contribute, and more interesting uses of the data will come to light.

My only concern is that I may inadvertently kill my site to death by overlooking some glaring reason that this is a bad idea.

So my question is: Is opening up the data from Bouldr a good / bad / stupid / dangerous idea, and why?

Cheers!

I'm on the verge of releasing the second version of an iPhone app as well as deploying several new features to Bouldr, however, I realize that the features themselves are not going to turn my site into a success.

My question is: Should I get a dedicated marketing persion on board, and if so, how should I go about finding and selecting them?

EDIT (in reponse to revorad)

A little more detail:

Bouldr (http://bouldr.net) is a worldwide guidebook for rock climbers and boulderers.

I'm in the process of building an iPhone application, and have released the first version already this year. From that, I drew on feedback, and have made numberous improvements and changes. The next version is just about ready, and once the last bug is smashed into the ground, I'll be submitting it for review.

I'll be building a free version of the app too - I'm building the paid version first so that I can get feedback from people that are genuinly interested in having Bouldr on their iPhone.

Ideally, I need to get lots more people adding and updating the site, and in order to do so, I think I need help from someone with the experience necessary to carry through.

I have a facebook fan page (http://facebook.com/bouldr), with ~14k fans, so I think I'm doing something right, but I also suspect that the message I'm sending is confused or at least not consise enough to stick.