Mobile Prototype Usability Testing: Methods and Best Practices

We specialize in usability testing of mobile app prototypes, offering both moderated and unmoderated options. Our certified UX researchers guarantee actionable insights. Tests start from $800 for a basic unmoderated session.

How to Conduct Usability Testing on Mobile App Prototypes

We run usability tests where a real person performs a task in a prototype, and we silently observe — no hints. That "silent" part is the hardest. The urge to say "no, tap here" kills the entire value of the test. The moment a user freezes for three seconds in front of a button that seems obvious to the team — that's the data. Our experience: 10+ years in mobile development and 50+ tests for fintech, e-commerce, and B2B apps. Every test will uncover critical issues before launch. Typically, 20% of problems account for 80% of user frustration.

How testing works

Test formats: moderated and unmoderated

Moderated usability test — a facilitator is present (online or in person), gives tasks, asks follow-up questions. Suitable for Figma/XD prototypes: the facilitator controls transitions between states that the prototype doesn't cover. Record via Zoom + device screen (iOS ReplayKit over AirPlay, Android via scrcpy or USB recording).

Unmoderated remote test — the participant runs the test independently, recording is sent automatically. Tools: Maze (integrates directly with Figma), Useberry, UserZoom. Maze provides automatic metrics: misclick rate, time on task, path analysis. For quantitative hypothesis validation — faster and cheaper than moderated.

The process involves:

1. Define objectives and tasks.
2. Prepare prototype and screening questionnaire.
3. Recruit target participants.
4. Run moderated or unmoderated sessions.
5. Analyze data and prioritize issues.
6. Report findings with video clips.

For mobile app prototypes, we prefer testing on real devices, not desktop. Figma Mirror or Maze on-device — the prototype opens on the participant's phone. Touch targets that work on a 1440p monitor break on a 360x780dp screen.

Why testing on real devices matters

Testing on a simulator does not replicate app behavior under real conditions: sensor sensitivity, network speed, overlays like notifications. We recorded a case where 4 out of 6 users could not tap the "buy" button because its bottom was covered by the iPhone X home bar. This was only revealed on a physical device. We use Lookback.io for moderated sessions and Maze for unmoderated.

How many participants do you need?

The classic Nielsen formula: 5 participants uncover 85% of usability issues for one user group (Jakob Nielsen, NN/g). In practice, 5–8 participants for a moderated test of one prototype. For unmoderated with quantitative metrics — at least 20 participants to achieve statistical significance.

Crucial: all participants must match the target profile. Testing with the wrong audience yields false insights.

How do we recruit participants?

We use a screening questionnaire covering demographics and usage experience. We filter out "professional testers" who know the scenarios. For B2B apps, we recruit via LinkedIn; for B2C, via targeted ads.

What we test and how we build tasks

Tasks are scenario-based, not directive. Not "click the registration button," but "imagine you want to create an account — do it." The task should describe the goal, not the path.

Typical task set for an e-commerce prototype:

• Find a product in category [X] and add it to the cart
• Place an order with delivery to a new address
• Find the status of your last order

After each task, we ask a Single Ease Question (SEQ): "How easy was it to complete this task?" on a 7-point scale. After the entire test, we use the System Usability Scale (SUS), 10 questions. SUS benchmark: above 68 is acceptable, above 80 is good.

Analysis of results

After each session — brief debriefing notes while fresh. After all sessions — affinity mapping of observations: which problems occurred with several participants, which are isolated.

We prioritise results using a frequency × severity matrix:

Deliverables

A report with video clips of key moments (timestamp + problem description), a prioritised list of UX problems, and fix recommendations with alternative solutions. Not just "button not obvious" — but "3 out of 6 participants tapped on the cart icon in the header instead of the floating button — consider replacing the FAB with an inline button on the product card."

What is included in the work?

• Development of scenarios and screening questionnaire
• Participant recruitment according to the target profile
• Conducting sessions (moderated/unmoderated)
• Data analysis with expert evaluation
• Preparation of a report with video, metrics, and recommendations
• Consultation on fixing identified issues

Timeline: from 2 to 5 business days turnkey. Write to us — we will evaluate your project for free. Contact us to discuss details.

Common questions: How many participants? For moderated, 5–8; for unmoderated, 20+. What metrics? SEQ, SUS, task time, misclick rate, path analysis. The report includes video clips and prioritized recommendations.

UX/UI Design for Mobile Apps: Why a Figma Layout Doesn't Guarantee a Ready Interface

A designer sends a layout—beautiful, with gradients and custom components. The developer opens it and realizes: the button is 36pt, the tap target is 20pt. On an iPhone SE, it's physically impossible to press with a thumb. The bottom sheet covers content when the keyboard appears. Navigation is built against the native iOS model. Apple will reject the app, or users will leave within a week—depending on how lucky you get with the review.

We have been designing mobile UX/UI for over 5 years and have seen hundreds of such situations. During this time, we have designed and helped launch 30+ mobile apps—from fintech products to social networks. You don't need to guess whether the design will pass App Review or Google Play—we embed platform requirements from the first screen. We'll assess your project in one day, contact us.

Mobile UX/UI is not an adaptation of web design. It is a separate discipline with specific platform constraints: safe area, touch gestures, UIViewController lifecycle, Activity state management.

Why Can't You Ignore Human Interface Guidelines and Material Design 3?

Apple HIG and Google Material Design 3 are not aesthetic recommendations. They are documented user expectations formed by years of using system applications. Expectations confirmed by user experience research on mobile platforms (User experience design).

HIG defines: minimum tap target 44×44 pt, safe area insets for notch and Dynamic Island, standard gestures (swipe back on iOS, back gesture on Android 10+). Ignoring safe area is a common mistake. safeAreaLayoutGuide in UIKit and safeAreaPadding in SwiftUI exist precisely for this. A designer who doesn't set safe area margins in Figma guarantees a bug during development.

Material Design 3 introduced Dynamic Color—the color scheme is generated from the user's wallpaper via MaterialTheme.colorScheme in Jetpack Compose. An app that ignores dynamic colors on Android 12+ looks out of place. This is not critical for niche products but is noticeable in mass-market apps.

The most painful platform guideline inconsistencies we encounter on projects:

• Custom navigation on top of system navigation. iOS users expect swipe back from any point on the left edge of the screen. A custom NavigationController without interactive gesture breaks this. Android users expect the system back button—a custom back button in the left corner does not fully replace it.
• Modal windows instead of navigation push. Bottom sheets are appropriate for actions, not for navigating content.
• Missing haptic feedback. UIImpactFeedbackGenerator on iOS is not decoration but part of the interface response. Buttons, swipes, and confirmation actions without tactile feedback feel broken.

Table: Comparison of iOS and Android UX/UI Requirements

How to Get the Most Out of Figma?

The Figma Variables API has changed the workflow. Design tokens—colors, typography, radii, spacing—are stored as variables and exported directly to code via figma-tokens or style-dictionary. This eliminates manual value transfer and desynchronization between design and implementation. Practice shows: Figma Variables speeds up asset handoff to development by 2–3 times compared to static frames, and using design tokens reduces code transfer errors by 60%.

Auto Layout with wrap and spacing between elements allows building components that behave like flex containers. A developer opens a component and sees not a static artifact but a description of behavior at different content sizes.

Component Properties—variants, boolean toggles, instance swaps—enable building a full design system right in Figma. A button with 4 states (default, hover, pressed, disabled), 3 sizes, and 2 icon variants is one component, not 24 frames.

Figma Prototype with Variables allows creating an interactive prototype with real state: showing how the screen changes with different variable values. This is no longer just a "clickable layout" but a full UX testing tool.

How to Benefit from Prototyping and UX Testing Before Development?

The most expensive mistake in a mobile product is to develop a feature, release it, and discover that users don't understand how it works. A Figma prototype at the testing stage costs zero development hours. Redoing a finished screen costs days. Testing a prototype before development begins reduces the number of fixes by 80%.

For usability testing, we use Maze (task testing on a prototype—the user goes through a scenario, we get heatmaps and mis-click rates) or direct sessions via UserTesting. Key metrics are task completion rate and time on task, not "like/dislike."

A/B testing on mobile is harder than on web: the App Store doesn't allow UI changes without an app update. Therefore, it's important to test hypotheses on a prototype before release, not through production experiments. According to research, fixing a bug found on a prototype costs 10 times less than after production release. And average task completion time increases by 40% after proper UX optimization during prototyping.

Why Are Animations Critical for Interface Perception?

Animations in mobile apps are feedback. An element doesn't appear instantly—it transitions to the desired state over 200–350 ms. This gives the brain context to understand what happened.

• iOS: withAnimation in SwiftUI, UIViewPropertyAnimator in UIKit for interactive animations with interruption capabilities. Spring animations with dampingRatio are the basis of most Apple system transitions.
• Android: AnimatedVisibility, animateContentSize, Crossfade in Compose. MotionLayout for complex scenes with multiple transformations.
• Flutter: AnimationController + Tween, Hero animations between screens, Lottie for After Effects exports. Lottie is especially effective for onboarding illustrations and empty states.

The key constraint is 16 ms per frame (60 fps) or 8 ms (120 fps on ProMotion devices). Animations must run on the GPU via CALayer/RenderThread, not on the CPU via layoutSubviews. Profiling via Core Animation instrument in Xcode is a mandatory step before releasing animated screens.

Why Is Accessibility Not an Optional Feature?

VoiceOver on iOS and TalkBack on Android are used by up to 15% of users—this statistic is confirmed by accessibility research described in Accessibility (Wikipedia). In absolute numbers for a large app, this is thousands of people. Additionally, App Store rejections due to accessibility occur, though rarely.

Minimum checklist:

• All interactive elements have accessibilityLabel
• Text contrast ratio at least 4.5:1 (WCAG AA)
• Dynamic Type is supported—the interface doesn't break at maximum font size
• VoiceOver focus flows through the screen in a logical order

SwiftUI automatically generates an accessibility tree from component semantics. UIKit requires manual setup of accessibilityTraits, accessibilityHint, and grouping via shouldGroupAccessibilityChildren.

What Does the Work Include?

The UX/UI design deliverables include:

What Is the Process and Timeline?

Design goes through stages: research and competitive analysis → user flows and wireframes → design system → UI layouts → prototype → testing → handoff to development.

Timeline estimates:

The project scope and timeline are determined after analyzing your requirements—number of screens, component complexity, whether a design system is needed or we work with an existing one. Get a consultation for your project—contact us for a preliminary assessment. Order a complete mobile app design—we'll assess your project in one day and propose the optimal work scope.