Thank you. That seems to be the feedback here (page isn't clear enough). Considering you run a service, how do you convey tell your users about new features in an engaging way?
At the moment I don't have a defined way of updating users of new features. As I'm aiming to run BugMuncher as openly and transparently as possible, a public road map has been on my todo list for quite a while. I'm very interested in your product, which brings me to my next bit of feedback:
I clicked the 'Get Early Access' button, and it opened what looked like it was going to be a survey, which put me off. I decided to give you the benefit of the doubt and clicked the 'Start' button, but my initial instincts where correct, and there where 8 survey questions to answer. I'll be honest, at that point I closed the tab and went about my day.
I'm BugMuncher's solo-founder and only employee, so all tasks fall to me, this makes me really value my time, to the point where those survey questions where enough to make me move on.
When someone clicks the early access button you should do nothing but capture their email address, so you can keep them updated and notify when beta access is granted. Once I've started using your product I'll be much more receptive to the survey.
I clicked the 'Get Early Access' button, and it opened what looked like it was going to be a survey, which put me off. I decided to give you the benefit of the doubt and clicked the 'Start' button, but my initial instincts where correct, and there where 8 survey questions to answer. I'll be honest, at that point I closed the tab and went about my day.
I'm BugMuncher's solo-founder and only employee, so all tasks fall to me, this makes me really value my time, to the point where those survey questions where enough to make me move on.
When someone clicks the early access button you should do nothing but capture their email address, so you can keep them updated and notify when beta access is granted. Once I've started using your product I'll be much more receptive to the survey.