This guide walks you through a structured UX audit for a mobile app in roughly four to six hours of focused work. You will identify usability failures, accessibility gaps, and friction points across core user flows, then produce a prioritised fix list your team can act on immediately.

What You'll Build

  • A heuristic evaluation scorecard covering ten usability principles across your app's key screens
  • A annotated screen inventory documenting friction points with severity ratings
  • A user flow breakdown showing where drop-off is most likely to occur
  • An accessibility checklist mapped to WCAG 2.2 Level AA criteria
  • A prioritised issue backlog ready to hand off to your product or development team

Prerequisites

Before you start, make sure you have the following in place.

  • Access to the live app or a high-fidelity prototype on iOS or Android
  • A Figma account (free tier is sufficient) for annotating screenshots
  • A spreadsheet tool such as Google Sheets or Notion for your scorecard
  • Screen recording software: iOS Screen Recording, Android's built-in recorder, or Mobbin for reference
  • Optionally, at least two to three recordings from real users via a tool like Maze or Lyssna (formerly UsabilityHub)

Step 1: Define the Audit Scope

A mobile UX audit without clear boundaries becomes a wish list, not a working document.

Start by listing the three to five flows that matter most to your business. For a SaaS app, those might be onboarding, the core task loop, and subscription upgrade. For an e-commerce app, focus on product discovery, cart, and checkout. For a healthcare or booking app, target registration, scheduling, and confirmation.

Write each flow as a sentence that starts with a user goal. For example: "A new user completes registration and reaches the home screen for the first time." This framing keeps your audit focused on outcomes, not just screens.

Common pitfall: Auditing the whole app at once. Auditing six flows in a day produces shallow observations. Two flows audited thoroughly produces actionable findings.

Step 2: Capture a Full Screen Inventory

Walk through each flow on a real device. Take a screenshot at every distinct screen state, including empty states, error states, loading states, and success confirmations.

Import every screenshot into a Figma file. Arrange them in flow order, left to right, on a single canvas. Label each frame with a short ID such as ONBOARD-01, ONBOARD-02, and so on.

Why does capturing error and empty states matter?

Most UX problems live in edge cases, not happy paths. A blank feed with no guidance, a form error that clears all fields, or a timeout with no retry option causes more churn than a slightly confusing navigation label. Capturing these states now means you will not miss them during evaluation.

Pro tip: Use Mobbin (mobbin.com) to benchmark your screens against comparable apps in your category. As of 2026, Mobbin indexes over 100,000 screens from iOS and Android apps globally, which gives you a fast reference for patterns your competitors use.

Step 3: Run a Heuristic Evaluation

Nielsen's ten usability heuristics remain the most widely used evaluation framework in professional UX practice. Apply them systematically to your screen inventory.

Create a spreadsheet with these columns: Screen ID, Heuristic Violated, Description of Issue, Severity (1 to 4), and Recommended Fix.

Use this severity scale, which maps directly to Nielsen Norman Group's standard rating system:

  • 1: Cosmetic problem only. Fix if time permits.
  • 2: Minor usability problem. Low priority fix.
  • 3: Major usability problem. High priority fix.
  • 4: Usability catastrophe. Fix before release.

Work through your Figma canvas screen by screen. For each screen, ask which heuristics are being violated and log every issue you find, no matter how small. Speed through this pass first, then go back and assign severity ratings.

Which heuristics catch the most mobile issues?

In mobile contexts, the heuristics that surface the most issues are: Visibility of System Status (does the app show loading, saving, or error states clearly?), Error Prevention (does it guard against irreversible actions?), and Flexibility and Efficiency of Use (can experienced users move faster through the app?). Plan to spend more time on these three.

Step 4: Map the Critical User Flows

Take your two to three priority flows and draw a simple flow map in Figma or on paper. Each step in the flow gets a node. Each decision point, such as a gate behind a permission request or a conditional screen, gets a branch.

Next to each node, annotate the following:

  • The primary action a user must take to proceed
  • Any friction you noticed during Step 3
  • The cognitive load required at this step (low, medium, or high)

Look for flows where a user must make more than two decisions in a row without feedback from the app. These sequences produce the highest drop-off rates. Research from Baymard Institute consistently shows that checkout flows with more than five distinct steps see abandonment rates above 70% on mobile.

Common pitfall: Confusing the number of screens with the number of steps. A single screen that asks for five separate inputs is five cognitive steps, not one.

Step 5: Run an Accessibility Check

Accessibility is not a bonus feature. In Australia, Canada, the US, and Singapore, digital accessibility obligations are enforced through legislation including the Disability Discrimination Act 1992 (AU), ADA Title III (US), and EN 301 549 equivalents adopted across multiple jurisdictions.

Check the following against WCAG 2.2 Level AA as a minimum baseline:

  • Colour contrast: Text must meet a 4.5:1 contrast ratio against its background. Use the Figma plugin Able or Stark to check this directly on your screenshots.
  • Touch target size: Interactive elements must be at least 44x44 points on iOS (Apple HIG) and 48x48 dp on Android (Material Design 3). Check your smallest buttons and icon-only actions first.
  • Text scaling: Run the app with your device text size set to the largest accessibility setting. Confirm that no text is clipped or overlaps other elements.
  • Screen reader compatibility: Enable VoiceOver (iOS) or TalkBack (Android) and navigate through your priority flows. Every interactive element must have a descriptive label. Decorative images must be hidden from assistive technologies.
  • Focus order: The logical reading order of the screen must match the visual order. On forms, the keyboard focus must move top to bottom, not jump around.

Log every accessibility failure in your spreadsheet with an automatic severity of 3 or 4. These issues directly exclude users and carry legal risk.

Step 6: Analyse Session Recordings and Funnel Data

Heuristic evaluation tells you where problems might exist. Behavioural data tells you where problems definitely exist.

If you have access to session recordings from a tool like FullStory, PostHog, or Smartlook, watch at least five recordings for each priority flow. Look for rage taps (repeated fast taps on an unresponsive element), hesitation before form fields, and unexpected back navigation.

Pull funnel data from your analytics platform. Whether you use Firebase Analytics, Mixpanel, or Amplitude, locate the step-by-step drop-off rate for each flow. Any step where more than 25% of users exit is a confirmed priority issue, regardless of its heuristic severity rating.

What if you have no analytics data yet?

If the app is new or analytics are not instrumented, use a lightweight remote testing tool. Maze and Lyssna both allow you to send unmoderated task tests to a panel in Australia, the US, Canada, or Singapore within 24 to 48 hours. Even five sessions per task will surface your most critical friction points.

Step 7: Build the Prioritised Issue Backlog

Combine your heuristic scorecard, accessibility checklist, and behavioural data into a single prioritised list. Sort it using this two-factor approach:

  1. Impact: How many users does this issue affect, and at what stage of the funnel?
  2. Effort: Is this a copy change, a design change, or a structural development change?

Issues that are high impact and low effort go into your first sprint. Issues that are high impact but high effort go into a planning discussion. Low impact issues of any effort level move to a backlog for later review.

Format each issue as a card with these fields: Issue ID, Screen ID, Description, Heuristic or WCAG Criterion, Severity, Recommended Fix, and Estimated Effort (S/M/L).

Share the Figma annotation file alongside the backlog. Developers and product managers make faster decisions when they can see exactly where on the screen the issue lives.

At Lenka Studio, this combination of annotated Figma files and a structured Notion backlog is the standard handoff format we use across product audits for clients in Singapore, Australia, and North America. It reduces the back-and-forth between design and development by a significant margin.

Step 8: Present Findings to Stakeholders

A UX audit that does not get actioned is wasted work. Structure your presentation around business outcomes, not design theory.

Lead with the data. Show the funnel drop-off numbers, the severity breakdown, and the number of WCAG failures. Quantify the impact where you can. If Step 4 of onboarding has a 40% drop-off rate, calculate what a 10% improvement would mean for monthly active users or revenue.

Group your findings into three categories for the audience: fix now (critical), fix this quarter (important), and fix when you can (minor). This framing respects the team's constraints and makes it easier for a product owner to turn your audit into a sprint plan.

Keep the presentation under 20 slides. Attach the full backlog as a linked document for anyone who wants the detail.

Frequently Asked Questions

How long does a mobile UX audit take?

A focused audit covering two to three flows typically takes four to six hours for an experienced UX designer. If you are new to heuristic evaluation or the app is complex, budget eight to ten hours. Include additional time for stakeholder presentation and backlog formatting.

Do I need real users to run a UX audit?

No. A heuristic evaluation is an expert review, not a user test. That said, combining expert review with even five user session recordings will catch issues that heuristics alone tend to miss, particularly in complex task flows or domain-specific apps.

How is a UX audit different from a usability test?

A UX audit is conducted by a designer evaluating the interface against established criteria. A usability test involves real users attempting tasks while you observe. Audits are faster and cheaper. Usability tests produce richer behavioural evidence. Both are complementary, not interchangeable.

Which accessibility standard should I use for a mobile app in Australia or Singapore?

Target WCAG 2.2 Level AA as your baseline. In Australia, the Disability Discrimination Act 1992 and the Web Accessibility National Transition Strategy reference WCAG. Singapore's Infocomm Media Development Authority guidelines also align with WCAG 2.1 AA minimum, and WCAG 2.2 is the current recommended standard as of 2026.

Can I run this audit on a prototype instead of a live app?

Yes, with some limitations. A Figma or Protopie prototype will let you evaluate visual hierarchy, layout, and basic flow logic. You will not be able to test real loading states, error handling, or screen reader behaviour accurately. For accessibility and performance checks, a live build on a real device is necessary.

Next Steps

Once your backlog is live, the next decision is sequencing. Start with the severity-4 issues and any WCAG failures before touching anything cosmetic. Run a follow-up session recording review after your first round of fixes to confirm that the changes resolved the observed friction, not just the theoretical issue.

If your audit reveals deeper structural problems with navigation, information architecture, or core user flows, those findings are the brief for a focused design sprint rather than a backlog fix.

If you want a second set of eyes on your audit findings, or need help turning a complex backlog into a phased design roadmap, the team at Lenka Studio works with product teams across Australia, Singapore, Canada, and the US to do exactly that. Get in touch and we can walk through your findings together.