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.
• Younger than 30 years
• 30 years or older
• In school
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.
Dream of Electric Sheep
android m-parking app