User Experience Stack Exchange is a question and answer site for user experience researchers and experts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

When creating a mobile application that uses crowd sourced information, what factors influence the usability and UX.

So in my case the information has already been crowd sourced by users of the website, its a music discography services of 90 dance, house etc. I'm creating a mobile application that allows these users to query this crowd sourced information on the go, in which they can view, and comment but not edit.

share|improve this question

closed as too broad by Graham Herrli, greenforest, Matt Obee, Alex Feinman, Benny Skogberg Nov 6 '13 at 10:39

There are either too many possible answers, or good answers would be too long for this format. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.If this question can be reworded to fit the rules in the help center, please edit the question.

this is a really vague question – DA01 Nov 4 '13 at 22:26
Hi @Luke. Welcome to the site! Can you edit your question to make it more specific? At the moment, it would be hard to answer with anything less than a full book of information. – Graham Herrli Nov 5 '13 at 1:26

Recently I took a survey asking people what they wanted from a mobile app in general and put the results up here. Although a lot of it seems like common sense (which it is) it gives you a good jumping off point from which to start.

A crowd-sourced app in particular is going to need good UX as it requires the user to do more than just use the app, they have to participate in it. From my experience creating this type of app you'll need to give users a "reward" for participating (points, prestige anything like that, much as Stack Exchange does) and make it easy enough for them to do that they won't fall at the first hurdle.

As a rule of thumb:

  • Only ask for information you need, lots of inputs will put users off
  • Make it easy for them to fill in the information you require by using the right type of input (for example if you want their email address then use an email field, this will swap the keyboard they see in the app to the email specific one)
  • Give the user something for their effort (be it a badge, some points or a tag that tells other users how awesome they are)
  • Let users chose to do things themselves. No pop ups or banners asking for users to do things, just make them aware of the ability to add/change/edit etc something and then leave them to decide if they want to.
  • Minimize the amount of personal data users have to enter. Unless you really need it don't ask for personal data, it makes users wary and less likely to want to contribute as they wonder what you want that information for.
  • Add a social aspect. From logging in using Facebook to posting to Twitter that they have done something to your app this gives the user incentive (and in the case of logging in it's much easier for the user) and allows users to interact with other people via the app. It also has the added bonus of marketing your app for you.
  • Don't expect every user to want to participate. Crowd sourcing is great, it gives a real human aspect to an app but not every user that installs it is going to want to add/change/edit things, some are going to be using it for reference, don't make them feel guilty or hinder this.

Unfortunately there doesn't seem to be much literature which is specific to crowd sourcing in mobile apps so checking the usual places such as Smashing Magazine's UX Site is probably the best thing you can do.
The main thing to do is apply common sense and ask yourself: "If I was going to use this app what would annoy me, and what would inspire me to contribute?"

share|improve this answer
+1 for a good answer to a vague question. – Jeremy T Nov 5 '13 at 21:09

Not the answer you're looking for? Browse other questions tagged or ask your own question.