Mobile

Use a Mobile Readiness Audit to inspect how a web experience behaves across desktop, tablet, and phone widths. The audit captures responsive browser evidence at 1440px, 768px, and 375px and checks console, link, accessibility, and layout risks. This is a responsive web audit; viewport screenshots alone do not establish native-device compatibility.

Run and review an audit

1. Choose a project and its main URL, or supply a URL you are authorized to test.
2. Ask your connected MCP client to start a mobile audit. Keep the returned audit ID and poll its status until it completes.
3. Retrieve the completed audit’s screenshots and scanner evidence. Review the observations before asking your agent to produce a qualitative report.
4. Render the structured report as HTML and PDF. Include the affected surface, severity, observation, evidence, and a concrete proposed fix for each finding.
5. Review the report before explicitly creating a public share link. Sharing makes the completed report available outside your workspace.

For example, ask: “Audit this project’s main URL at the supported responsive widths. Wait for completion, inspect the screenshots, and summarize the most significant layout and accessibility findings with evidence. Do not share the report yet.”

The report-rendering tool accepts an agent-authored report; it does not call a QualityMax model itself. Model requirements and costs depend on the client you use. An audit score is a triage aid, not a certification of accessibility or device coverage.

See the mobile MCP reference for start_mobile_audit, status and evidence retrieval, report rendering, sharing, and audit history. The MCP quickstart explains account connection.

Turn findings into follow-up work

The report parser accepts extracted report text or a PDF and returns structured findings. Parsing does not change project data. Review the extracted findings before creating work or applying changes.

For supported managed mobile flows, update_mobile_flow validates the current canonical QTML flow and recompiles it. Execution supports verified generated Appium flows through the documented execution tools. This does not imply that arbitrary Appium projects or a general-purpose physical-device fleet are available.

See test execution tools and QTML exports for the relevant contracts. Review the changed flow and its completed execution evidence before considering a repair verified.