Surver about survey

---

We all know -- getting the user feedback is essential, but it's hard. At least I find it so.

For example, judging from data gathered from random Android app and game samples, on average:

• about 10-20% of all users that have downloaded the app, have actually reviewed the app,
• about 10% of those that reviewed the app also leave a comment (making the number of comments approximately 1-2% of all downloads),
• about 1% of users communicate via in-app channels,
• about 1% of users respond to social posts.

As I mentioned already, this is based on a random sample and the rather small sample size (10) may be biased by statistical error. Nevertheless, it "feels" right

Now, let's say that your user base is wide enough to get the accurate feedback about your product, but only if you could motivate more users to respond to Rate and Leave Feedback requests... but let's leave that for a separate discussion.

What I wanted to ask you all is:
Which questions would you ask your users if you knew they will answer truthfully?


Think survey!
Think user satisfaction!
Think best loved feature!

Don't think girl's/boy's phone numbers! :P


In the end, I'll try to compile the result in a single survey separated in categories (and based on the popularity of suggested questions) for the community to use.

Let's start asking

<placeholder>

Starter

---

To get us going, here're some example questions (courtesy of zoomearng.com):

• What Features Can You Not Live Without? – Asking people what features they must have on your upcoming product is a great way to find out what is in the highest demand. In short, this online survey question shows you, overall, what features you cannot leave out.
• What Is the Most You Would Pay? – Understanding your potential customer’s price range can help you better understand what you can realistically afford to include, and exclude, to hit those price points.
• What Did You Like Best About Our Old Product? – If you had an older version of a product and are updating it, finding out what features your customers liked best. Use this online survey question to find out what you should not change in future versions of your product.
• What Other Brands Would You Consider? – This online survey question helps you quickly locate and understand your possible competition. Knowing what you’re up against will help you better gauge where your energies should be focused for your product.
• What Else Should We Know? – Let your online survey respondents have the floor. This question gives them the opportunity to sound off about things maybe your online survey questions missed. Find out all you forgot to ask about with this question.

One thing that I was not sure how to proceed is the personall, demographic questions. How deep to go and what are the limits?

I believe that the answer to this is in type of survey, but also in giving the user the possibility to opt-out or to make those questions non-mandatory.


What's the safe zone with demographic questions?

I think you can safely ask for:
Country
Age
Occupation
Service Provider(if any, or if necessary)

Another question that can be considered is "Do you primarily use this app for business or personal use?" Obviously only certain apps would use this.

Just a suggestion, but since a lot of questions could vary between apps(like between recreational or utility apps) maybe if you made a tool that allowed app developers to customize and then compile a survey which can then be added to their app with minimal effort it would be awesome. That way developers could ask more app specific questions alongside the more general ones you mentioned above. The hardest thing about that would probably be making it compile into a universal format that can be copy pasted into any apps code, but I'm sure it's not too hard. If the tool automatically created the proper classes along with each survey then it literally could be copy pasted into whatever part of the app the dev wants it in.

Just my 2 cents.

Sent from my HTC Glacier using XDA

Good suggestions, AlanB412.

The Country and Service provider are quite well covered by Play Store statistics (though, should be considered in case app is not published on Google).
Other "personal" stuff, I compiled into one (multiple choice) question for the survey I'm creating for m-parking:

Please tell us something about yourself. Check all that apply.
• Female
• Male
• Younger than 30 years
• 30 years or older
• In school
• Employed
• Unemployed

The details of occupation, like industry and field of work, deserve a dedicated question, if needed, of course.

Ideally, the availability of questions should be dependent on previously made choices (e.g. occupation industry should be asked only if employment status "employed" or "self-employed" were previously selected). That kind of branching should make the survey more engaging as opposed to presenting the user with irrelevant questions.

The idea about the "tool" for developers sounds interesting.
How I'm looking at is a library project that has many out-of-the-box available questions, but that allows also for customizations and works dynamically with any question specified in standard strings dedicated resources.

The tricky part is actually not the inclusion of such Survey-library in apps or its dynamic handling of question-answer configuration. It's in (collecting) the reports part. For that to work seamlessly out-of-the-box, a third party "cloud" reporting service should be available -- to collect and provide access to reports.