I developed an Android application and I want to make a survey/questionaire about the usability, user interface, user experience etc. of my application to get some feedback from users. But I don't know which kind of questions to ask...

I would like to know If there are some links/tools/books that can help me.

Can you explain how you plan to use the questionaire - is it to perform a user test in person? Will it be sent out via email? Or will it pop up in the screen during use?
–
Lisa TweedieJun 17 '12 at 21:59

Or you could record the session directly using a usability sled and see where the user's got confused, hesitant or lost.
–
Neon22Oct 25 '13 at 11:30

2 Answers
2

I am going to assume that by questionaire you mean survey (i.e. one that pops up or that you send out by email).

In terms of getting people to respond to such a questionaire the key thing is to keep it short and allow them the opportunity to end it and any point i.e. without quitting and losing all the data!

In all the questions try and do the work for them - so they can respond with a minimal number of clicks.

Generally surveys start by finding out a bit about who the user is e.g. How long they have had a smart phone, do they rate themselves as technical, male/female, if you go for age do it in buckets so that people don't have to identify their exact age. But again limit it to just what will be useful to you.

For the questions themselves you should generally ask closed questions e.g. where they can select one from three answers or use a rating scale (with a slider or radio buttons).

You can probably get away with one or two open questions. Although you could provide an add comment button next to each statement ... in case they felt they wanted to add an explanation.

To get an initial set of questions to ask I would brainstorm with my colleagues to find issues that will affect design decisions. Identify some questions. Then walk through your best guess at the answers ... would that information be useful to you? What would you do with it? What if the answer was the opposite. What would you do then?

The only way to test out your questionnaire is to pilot it with a few users (could be anyone someone in your office, friends...). This is the best way to fine tune what needs to be asked.

The queen of forms and questionaires has to be Caroline Jarrett - here is a great slideshow she did on designing surveys in 2011 and this one in 2012 (read both they are different).
Here is a podcast on surveys from April 2012.

Designing an effective questionaire is also about asking them in the write way and well designed. Caroline's book forms that work has to be the key reference here too.

For instance the picture below demonstrates lots of best practice for mobile. I love how the question is the focus and is very large (no fiddling around to press tiny buttons). I think the use of a slider control with a big button is great (notice how minimal they have been with the data ink on the scale). I assume they swipe to move on. Notice how the user can submit at any point. I would probably have added a number of steps e.g. 1 of 5. to encourage them to get to the end. Otherwise perfect.

Thanks for your answer! I think that I have here enough information to start... :)
–
ampJun 17 '12 at 23:21

1

No worries. I think you should edit your question to something like "What is best practice for UX surveys of a mobile application?" And also provide some context for how you want to use the survey. You might get even more useful info (:
–
Lisa TweedieJun 17 '12 at 23:32

Well, the ideal way to discover usability issues with with in-person user testing, so if you think you could arrange a session with, say, five or six participants, that would be best. You can get much, much richer data that way - some usability issues are very difficult to capture by Q&A.

Still, questionnaires aren't useless - though they will be affected by response bias (as well as self-reporting issues, memory biases and 'response acquiescence', where participants will tend to agree with statement questions). What sorts of questions you ask will depend on the kind of application you're talking about, and issues you already expect to see, but some starting points are:

Did you always feel like you knew what to do and where to click?

Did you ever do something and got an unexpected result?

Did you feel you could trust the application and the organization behind it?

Did you find the application attractive?

Did this application act and feel like other, more familiar applications?

How quickly could you get what you wanted with this application?

As for designing the questionnaire, you might be interested in this article by Nokia on mobile questionnaires for smartphone apps.