Qualitative data is OK, but without a really strong understanding of social theory and stuff like desirability bias there's a big risk of not asking the right questions and making misinformed decisions.<p>One way we've found to limit this risk is by supplementing hypotheses developed through qualitative research with a quantitative approach.<p>So, ask users what they like/dislike about an experience to formulate an idea of what changes to your app may better the experience, BUT make sure to then TEST those changes using a rigorous method (i.e.: experimentation or A/B testing) to validate that the feedback you're hearing is not just noise...
As long as the message is nog pushed in people's faces and they can voluntarily give their input this could be interesting for us.<p>We need to ask our users for which stocks they like to trade in our gamified trading app. And it could also help us learn more about our users (have they trade before? Where?).<p>You need to know very specifically what you want to find out.
Good to see real numbers in these sort of articles..<p>But let’s face it - users are never going to tell you what they need...or what you should build.<p>Shouldn’t they have spent more time building a great product first - before launching it? Those retention numbers to me say the product wasn’t working.<p>I doubt Apple asked any users for input when coming up with the iPhone.
So I checked out the code on github and and it looks pretty simple, especially the integration part. But to integrate requires developers to clone the codes in our projects. Might be a hassle if updates and fixes roll out after the integration.
Hey Simon here, one of the co-founders.. Antony and I would love your feedback, especially the areas for improvement<p>direct link: <a href="https://polljoy.com" rel="nofollow">https://polljoy.com</a>
I could have used the type of feedback you're talking about at my failed startup. We found it very difficult to get an honest answer about why we had no traction. Keen to see where this goes.