Which task were you trying to complete on your phone?
Identify the task and its mobile context without requesting precise location or unrelated device information.
Product and software research / Survey guide
Product and software research · Practical field guide
Mobile app feedback survey
Identify friction specific to small screens and use on the move.
Opens product registration. Example questions are not imported automatically.
FOLLOW THE FEEDBACK
- Understand the context
Which task were you trying to complete on your phone?
- Investigate the friction
Was any control or text difficult to use?
- Choose a next check
Which action needed a larger touch target?
A planning aid, not automated analysis of your answers.
Read the answers carefully
What the answers cannot tell you.
Do not generalize a desktop issue to mobile without checking the device context.
Example answers identify a control that is easy to see on desktop but hard to tap on a phone. This is an illustrative interpretation problem rather than a real customer result. Review the touch target and test the same task at mobile sizes.
A useful starting point
A questionnaire for mobile app.
Identify friction specific to small screens and use on the move. Choose the questions that fit the experience you are investigating; avoid asking people to evaluate a step they did not encounter.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate.
Was any control or text difficult to use?
Separate readability and touch-control issues from the underlying task's complexity.
What would you prefer to do later on a larger screen?
Find work the respondent would move to a larger screen without assuming every task should be optimized for mobile completion.
Was it easy to resume the task after an interruption?
Check whether interruption loses context, progress, or confidence; these require different design responses.
Which action needed a larger touch target?
Name a control that was difficult to tap rather than asking only for a general mobile satisfaction rating.
If nothing was unclear or difficult, say so. Skip questions about steps you did not experience; use not applicable where appropriate. Which task were you trying to complete on your phone? Was any control or text difficult to use? What would you prefer to do later on a larger screen? Was it easy to resume the task after an interruption? Which action needed a larger touch target?
Download the questions as text ↓
Examples to adapt, rather than a validated research instrument.
A worked interpretation example
From a comment to a practical next step.
Illustrative scenario. These are not customer results.
Keep the finding specific
Example answers identify a control that is easy to see on desktop but hard to tap on a phone.
Choose an action to test
Review the touch target and test the same task at mobile sizes.
Check the experience again
After testing the action, revisit this original observation: Example answers identify a control that is easy to see on desktop but hard to tap on a phone. Repeat the relevant experience prompts with people who encountered the change. Compare specific explanations and sample differences; do not claim causation from the before-and-after responses.
Before you send it
Check what your wording assumes.
Would you agree that mobile app feedback was a completely positive experience?
Which task were you trying to complete on your phone?
The initial wording assumes a positive evaluation. The revised question asks about the actual situation so a respondent can describe difficulty, uncertainty, or a different experience.
Choose the response format
Make room for the explanation.
| Question | Suggested format | What to preserve |
|---|---|---|
| Which task were you trying to complete on your phone? | Short open text | Identify the task and its mobile context without requesting precise location or unrelated device information. |
| Was any control or text difficult to use? | Short open text | Separate readability and touch-control issues from the underlying task's complexity. |
| What would you prefer to do later on a larger screen? | Short open text | Find work the respondent would move to a larger screen without assuming every task should be optimized for mobile completion. |
| Was it easy to resume the task after an interruption? | Short open text | Check whether interruption loses context, progress, or confidence; these require different design responses. |
| Which action needed a larger touch target? | Short open text | Name a control that was difficult to tap rather than asking only for a general mobile satisfaction rating. |
Make questions optional where appropriate. If you add a rating scale, label its endpoints, keep one idea per question, and retain a follow-up for reasons. These examples are not a validated measurement instrument.
Inside the product
Build and preview your questionnaire in SurveyTeams
Build questions around an experienced task, keeping reports of difficulty separate from feature preferences. The actual product screenshot shows a separate synthetic post-event demonstration; the example questions on this page are not already loaded in the product.
- Start a manual draft with a title that tells respondents why you are asking. Identify friction specific to small screens and use on the move.
- Copy or download the relevant example questions above, then create and add the questions in your draft. Review the question notes before deciding which prompts to keep.
- Check the respondent preview, especially this wording: “Which task were you trying to complete on your phone?” Include a way to say none or not applicable, and review your response-handling instructions.
Screenshots demonstrate creation and preview. Distribution and results are separate steps; availability varies by account and plan.
Build with SurveyTeams
Build your own mobile app questionnaire.
Use these examples to draft your questionnaire. Create a survey draft, add questions, and check the respondent preview in SurveyTeams. Additional features depend on your account and plan.
Create your survey in SurveyTeams
Opens product registration. Example questions are not imported automatically.
Learn about the product ↗From question to next step
Make the feedback useful.
Set the decision
Write down the decision you want this questionnaire to support: identify friction specific to small screens and use on the move.
Invite relevant voices
Invite people who experienced the relevant situation. Explain response handling and include an optional skip or not-applicable route. Do not generalize a desktop issue to mobile without checking the device context.
Choose an action
Review the touch target and test the same task at mobile sizes.
Before you send it
Questions, answered.
What should I learn from this mobile app questionnaire?
Identify friction specific to small screens and use on the move. Start with one decision you can act on rather than using the survey to confirm a preferred answer.
What should I look for in the answer to “Was any control or text difficult to use?”?
Separate readability and touch-control issues from the underlying task's complexity.
What would a practical next action look like?
Review the touch target and test the same task at mobile sizes. This is an example action to investigate, not a guaranteed improvement.
When should I send this questionnaire?
Ask after respondents have experienced the specific situation in the first prompt: “Which task were you trying to complete on your phone?” Allow enough time after a proposed change for people to experience it before repeating the questionnaire.
What should I check after changing the process?
After testing the action, revisit this original observation: Example answers identify a control that is easy to see on desktop but hard to tap on a phone. Repeat the relevant experience prompts with people who encountered the change. Compare specific explanations and sample differences; do not claim causation from the before-and-after responses.
Can I use these questions in SurveyTeams?
Copy the questions or download TXT, CSV, JSON, or a Markdown worksheet and adapt them in your own survey. The product CTA opens registration and does not import the example. Verify the features and terms available in your account.
Does the product screenshot contain this questionnaire?
It shows a separate synthetic event-feedback example used to demonstrate the real builder. Copy or download the questions on this page and adapt them in your own draft. Registration does not import them automatically.
Continue exploring