Have you ever watched someone use your mobile app and wondered what they're actually thinking? I've been working in mobile app development for over eight years, and I can tell you that watching users interact with an app is one thing—but hearing their thoughts out loud is completely different. That's where user testing sessions come in, and more importantly, the questions you ask during them.
User testing isn't just about putting your app in front of people and hoping for the best. It's about having structured conversations that reveal the truth about how your app really works in the real world. The questions you ask can make or break these sessions; ask the wrong ones and you'll get surface-level feedback that doesn't help anyone. Ask the right ones and you'll uncover insights that can transform your app's user experience.
The best user testing sessions feel like friendly conversations where users forget they're being observed and start sharing their honest thoughts
Good UX research through interview techniques starts with understanding that users don't always say what they mean or mean what they say. They might tell you they love a feature whilst their body language suggests they're confused by it. That's why the questions you ask need to dig deeper than "do you like this?" You need questions that reveal behaviour patterns, uncover pain points, and help you understand the why behind user actions. This guide will walk you through the specific types of questions that get results.
Types of Questions to Ask During User Testing
Getting the right information from your user testing sessions comes down to asking the right questions—but not all questions are created equal. I've learnt over the years that the type of question you ask can dramatically change the quality of feedback you receive, and honestly, it took me longer than I'd like to admit to master this skill.
There are three main types of questions that work well in user testing sessions. Open-ended questions give users the freedom to express their thoughts without leading them in any particular direction. Questions like "What are your thoughts on this screen?" or "How would you describe your experience so far?" let users share what's actually on their mind rather than what they think you want to hear.
Task-Based Questions
Task-based questions are brilliant for understanding how users interact with your app. Instead of asking "Do you like the checkout process?" try "Show me how you would purchase this item." These questions reveal the gap between what users say they do and what they actually do—and that gap can be quite revealing.
Follow-Up Questions
Follow-up questions are where the real gold is found. When a user says something interesting, dig deeper with "Can you tell me more about that?" or "What made you feel that way?" These questions uncover the reasoning behind user behaviour, which is what you really need to improve your app.
The key is mixing these question types throughout your session. Start with open-ended questions to set the tone, use task-based questions to observe real behaviour, and follow up with probing questions to understand the why behind user actions.
Questions About Navigation and User Flow
Getting around your mobile app should feel natural—like walking through your own home with your eyes closed. When users struggle to find what they need or get confused about where to tap next, that's when they delete your app and move on to a competitor. Through years of conducting UX research sessions, I've learned that asking the right questions about navigation can reveal problems you never knew existed.
Start with simple questions that don't feel like a test. "Where would you go to find your previous orders?" or "How would you get back to the main screen from here?" These interview techniques help you understand if your navigation matches what users expect. Don't ask leading questions like "Do you think the menu button is easy to find?"—instead, watch what they do naturally and ask them to talk through their thought process.
Uncovering Hidden Navigation Problems
The real gold comes from questions that reveal deeper issues. "What did you expect to happen when you tapped that?" and "Where do you think this button will take you?" can expose mismatches between your design intentions and user expectations. Sometimes users will say everything is fine, but their actions tell a different story.
Ask users to complete a task without giving them step-by-step instructions. Their natural behaviour will show you exactly where your navigation breaks down.
Questions That Reveal User Flow Issues
Focus on the journey, not just individual screens. "How would you go about completing this task?" followed by "Was that what you expected?" can reveal whether your user flow makes logical sense. Pay attention when users backtrack or seem uncertain—these moments often highlight the biggest opportunities for effective mobile app UX design improvement.
Questions About Content and Features
When you're testing your app with real users, understanding how they interact with your content and features is absolutely critical. I can't tell you how many times I've seen brilliant functionality go completely unnoticed because users simply didn't understand what it was for or how to use it.
Start by asking users what they think each feature does before they actually use it. This gives you insight into whether your feature names and descriptions make sense. Then watch them try to complete specific tasks—can they find what they're looking for? Do they understand the purpose of each screen?
Key Questions to Ask About Content
- What do you think this button/feature does?
- Is there too much or too little information on this screen?
- What would you expect to happen when you tap this?
- Can you find the information you need quickly?
- Does this text make sense to you?
- What's missing from this page that you'd expect to see?
Pay close attention to how users describe your features in their own words. Their language is often much clearer than whatever we've come up with internally. If someone calls your "Quick Actions Panel" the "shortcut menu", that's probably what you should call it too.
Testing Feature Discoverability
One thing I always test is whether users can actually find the features you've built. You might have spent months perfecting a particular function, but if users can't discover it naturally, it might as well not exist. Ask users to explore freely and tell you what they notice—you'll be surprised by what they miss and what catches their attention instead. Before building complex features, it's worth considering whether your app idea addresses real user needs.
Questions About Visual Design and Interface
When testing your mobile app's visual design, you need to dig deeper than just asking "do you like how it looks?" That's not going to give you the insights you need to make real improvements. The visual design of your app can make or break the user experience—and I'm not being dramatic here. If people can't find what they're looking for or feel confused by your interface, they'll delete your app faster than you can say "user retention".
Start with questions about clarity and readability. Ask users to point out any text that's difficult to read or buttons that don't look clickable. "Can you see this text clearly?" and "What do you think will happen when you tap this?" are simple but revealing questions. You'd be surprised how often developers assume something is obvious when it really isn't to users.
Colours, Icons, and Visual Hierarchy
Ask users about the colour scheme and whether different elements feel connected or separate. "Do these screens feel like they belong to the same app?" helps identify inconsistencies that can damage brand consistency in mobile app development. For icons, try "What do you think this symbol means?" without explaining it first. If users can't interpret your icons correctly, you've got a problem that needs fixing.
Good design is invisible—when users struggle to understand your interface, the design has failed its primary job
Test your visual hierarchy by asking users to scan a screen and tell you what catches their attention first, second, and third. This reveals whether your most important elements are actually standing out. Questions like "What's the most important thing on this screen?" will show you if your design is guiding users' eyes where you want them to go. If you're still in the planning phase, creating wireframes for your mobile app can help establish this hierarchy early.
Questions About Performance and Technical Issues
Performance problems can kill even the most brilliant app idea—and users won't hesitate to delete something that doesn't work properly. During testing sessions, you need to dig deep into how your app performs under real-world conditions, not just in your controlled development environment.
Start by asking users about loading times and responsiveness. "How did the app feel when you were navigating between screens?" and "Did anything feel slow or unresponsive?" are good starting points. Users will often notice lag before you do, especially on older devices or slower network connections.
Battery and Device Performance
Don't forget to explore how your app affects their device. Ask "Did you notice your phone getting warm while using the app?" or "How's your battery level compared to when we started?" These might seem like minor details, but apps that drain batteries or overheat devices get uninstalled fast.
Error Handling and Edge Cases
Test what happens when things go wrong. Ask users to try actions with poor internet connection or when certain features aren't available. "What happened when you tried to upload that photo?" or "How did the app behave when your connection dropped?" will reveal gaps in your error handling. For Android developers specifically, proper Android app development practices can help prevent many of these issues.
Here are key performance questions to include in your testing sessions:
- Did any screens take longer than expected to load?
- How did the app respond when you switched between it and other apps?
- Were there any moments when the app felt frozen or unresponsive?
- Did you encounter any error messages, and were they helpful?
- How well did features work with a poor internet connection?
Remember, users won't always volunteer information about technical issues—you need to ask directly and observe their behaviour carefully.
Questions About Overall User Experience
The overall user experience is what makes or breaks a mobile app. You can have the prettiest interface in the world, but if users feel confused or frustrated after using your app, they won't come back. That's why asking the right questions about the complete user journey is so important during your UX research sessions.
Start with the big picture questions. Ask users how they feel after completing their tasks—were they satisfied, frustrated, or somewhere in between? This gives you insight into their emotional state, which is just as important as whether they technically completed what they set out to do. Don't be afraid to ask follow-up questions here; sometimes users need a moment to process their experience.
Understanding User Satisfaction
The most valuable interview techniques often involve asking users to compare their experience. Try questions like "How does this compare to similar apps you've used?" or "What would make you choose this app over others?" These questions help you understand where your mobile app stands in the competitive landscape and what unique value it provides. Consider that many successful businesses are now adopting mobile-only strategies based on user preferences.
Ask users to describe your app to a friend in their own words. This reveals how they truly perceive your app's purpose and value—often quite different from what you intended!
The Complete Journey
Finally, ask about their likelihood to continue using the app and recommend it to others. These questions predict real-world behaviour better than most other metrics. Users might complete tasks successfully during testing but still have no intention of returning. Understanding why gives you the insights needed to create genuinely engaging experiences that keep people coming back.
Conclusion
User testing sessions are only as good as the questions you ask during them. After eight years of working with mobile app clients, I can tell you that the difference between a successful testing session and a waste of time often comes down to preparation and asking the right things at the right moments.
The questions we've covered in this guide—from navigation and user flow to performance issues and overall experience—form the backbone of any solid testing approach. But here's what I've learned: you don't need to ask every single question in every session. Pick the ones that matter most for your current development stage. If you're testing a prototype, focus on navigation and flow. If you're close to launch, dig deeper into performance and polish.
What really matters is listening to what users aren't saying as much as what they are. Watch their faces when they get stuck. Notice when they pause or hesitate. These moments often reveal more than direct answers to your questions.
One more thing—and this is something I wish more clients understood from the start—user testing isn't a one-time event. The best apps come from teams that test early, test often, and aren't afraid to ask uncomfortable questions about their design choices. Your users will thank you for it, and more importantly, they'll actually use your app when it launches.
The questions in this guide will get you started, but don't be afraid to adapt them based on what you're learning about your specific users and their needs.
