Understanding Mobile App Users: Research Methods and Results

Clients often arrive with a ready-made concept. After our UX research, we discover that the real user pain points lie elsewhere. The gap between what people say and what they actually do is a key problem that research must capture. A project that skips this stage risks wasting budget on untested hypotheses and losing 30% to 50% of potential conversion.

Over 5 years, we have conducted more than 50 UX research studies for mobile apps—from fintech to delivery. Our experience shows that investment in research pays off 10 times over by reducing late-stage rework. For example, a typical $4,000 study can prevent $40,000 in rework costs.

Why Conduct Research Before Design?

Design built on assumptions leads to rework. Fixing an error during development costs 10 times more than during research. For mobile apps this is especially critical: every UI change requires a new build, store review, and QA. Research upfront reduces the number of iterations by 40% and speeds time to market. Early research is 3 times more effective than post-design fixes in reducing budget overruns.

Which UX Research Methods Are Suitable for Mobile Apps?

The choice depends on the project stage and the type of question. Below is a comparison table of the main methods we use.

In-depth Interviews (Contextual Inquiry) — for open-ended questions: "How do you currently solve this task? Show me what you do on your phone." We record the participant's screen via screen recording permission on iOS (ReplayKit) or AZ Screen Recorder on Android. We analyze actions, not answers: where the user hesitates, where they tap instinctively, what they ignore.

Card Sorting — to validate information architecture before design. Online sessions via Optimal Workshop's OptimalSort: users sort function cards into groups and name them. With 20+ participants, patterns become clear. The result is a similarity dendrogram that directly affects navigation taxonomy. Learn more about the method on Wikipedia.

Tree Testing — to test a completed hierarchy. We show a text-only tree (no design), give tasks like "find section X". Optimal Workshop's Treejack provides metrics: success rate, directness rate, time on task. Benchmark: success rate above 78% for key tasks. If lower, revisit navigation before wireframes. Tree testing is 5 times faster than user interviews for validating navigation.

Heuristic Evaluation — audit an existing app against Nielsen's heuristics. Quick (1–2 days), yields a prioritized list of specific UX problems. Suitable for improving an existing product rather than building from scratch.

Analytics + Session Recording — for products with a user base. Integrate Firebase Analytics + Mixpanel for event tracking; Smartlook or UXCam for session recording on mobile (with automatic hiding of sensitive fields). Mobile heatmaps work differently than web: instead of click heatmaps, we aggregate touch areas. Session recording helps identify 85% of usability issues.

Example: For one fintech app, we conducted in-depth interviews and found that users did not understand the term "overdraft". We replaced it with "credit limit" — conversion to application increased by 15%. This is a direct proof of research's economic efficiency.

Effectiveness of Research Before vs. After Design

Research before design reduces budget risk and speeds time to market. Comparison shows it is 3 times more beneficial than rework during development.

Our Research Process: Typical Workflow

1. Formulate research questions — not "what do users think", but specific: "How do current solution users search for [task X]? What mental objects do they create for this?"
2. Screen and recruit participants — for B2C apps we use User Interviews, Respondent.io, or local panels. Screening criteria: not demographics but behavioral: "uses mobile app for [task] at least 2 times per week". Our target audience research ensures representative participants.
3. Conduct sessions — interviews 45–60 minutes, online via Zoom with recording (with consent). Semi-structured protocol: contextual questions first, then task-based part.
4. Analysis — Affinity Mapping in FigJam. Each observation is a card; group by patterns. Thematic analysis, not quote quantification.
5. Synthesis — personas (if not existing), jobs-to-be-done formulations, list of insights prioritized by frequency and criticality.

The full cycle with 8–12 participants takes 3–5 business days including recruiting and analysis.

What's Included in Our UX Research Service

• Insight report: interpretation and recommendations, not just quotes.
• Prioritized list of problems and opportunities.
• Jobs-to-be-done formulations for key scenarios.
• Raw session materials (recordings, transcripts, affinity diagram) — on request.
• Access to tools and methodology for self-repetition.
• Additionally, we provide documentation of the research methodology, training for your team on how to conduct similar studies, and post-project support via email for 2 weeks.

Typical Mistakes in Recruiting

Recruiting "convenient" participants — colleagues, friends, loyal customers. They give socially desirable answers and do not represent the real audience. Another pattern: conducting research after the design is done. At that stage, the team seeks confirmation, not insights, and tends to ignore criticism.

Our services include usability testing for validation. We focus on user experience analysis to uncover needs. We specialize in mobile app UX research using various methods.

Get in touch to discuss UX research for your mobile app. Our expertise and extensive experience guarantee practical results that pay off.

Request a consultation: we will help select methods that fit your budget and timeline. The cost of research depends on the number of participants, methods, and recruiting needs — calculated individually. Typical studies range from $3,000 to $8,000 for a qualitative round, with ROI exceeding 10x.

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.