# NATIVE MOBILE

## Test every device your customers use, not just the one on your desk

Run a mobile test once, and Applitools replicates it across real and emulated iOS and Android devices with Visual AI, so a layout break on one screen size doesn't reach the one you didn't check.

[Try for free](https://auth.applitools.com/users/register)

## Catch what only shows up on some devices

A layout that's fine on your test device can break on a smaller screen or an older OS. Visual AI checks every device the same way, not just the one you happened to run on.

## Stop chasing broken locators

Mobile locators shift between OS versions and app updates. Visual AI finds elements by what's actually on screen, not by an ID that changed underneath it.

## Run once, cover every device

Record a test against one device and replicate it across the rest of your device matrix, instead of writing and maintaining a separate script for each one.

## How Applitools tests native mobile apps

## Run once, validate everywhere

**Native Mobile Grid** Run your test against one real or emulated device, and Applitools replicates the same checkpoint across the rest of your device matrix in minutes, not hours.

**Broad device and OS coverage** Test against a broad matrix of iOS and Android versions and screen sizes, without owning, provisioning, or maintaining the hardware yourself.

## Stop rewriting tests when locators break

**Visual AI instead of brittle IDs** Eyes finds elements by what's actually on screen, so a locator that changed between app versions doesn't take your test down with it.

**One line of code** Add a visual checkpoint to an existing Appium, Espresso, or XCUITest script without rebuilding your test suite.

## Ignore the differences you expect

**Region-based comparison** Mark a part of the screen that's supposed to change, like a live price or a personalized banner, so it doesn't fail a test that's otherwise correct.

**Match levels for layout or content** Choose Layout when position matters more than pixel-perfect content, useful for testing the same screen across languages without writing a new assertion for each one.

## Find the real cause of a failure

**See what changed in the view hierarchy** When a test fails, see the exact element and layout change behind it, so you know if it's a real bug or an expected update.

**Auto-maintenance in bulk** Approve or reject every story affected by the same intentional change in one action, instead of reviewing each one on its own.

## Integrate Applitools into your tech stack

Applitools works with 50+ major testing frameworks and languages, source code tools, CI/CD tools, and collaboration tools.

## What backs up every Storybook test

# 1

## Broad format coverage

Extend the same visual checks across native mobile, mobile web, and desktop, so a regression doesn't slip through in a format you didn't think to test.

# 2

## No hardware to maintain

Test across a wide matrix of iOS and Android versions and screen sizes without owning, provisioning, or maintaining physical devices yourself.

# 3

## Local AI processing

Visual comparisons run locally within your environment. Component snapshots are never sent to an external model or used for training.

# 4

## Deterministic execution

The same screen, device, and test always produce the same result, so a pass is something you can trust and a failure is a real regression, not a flaky run.

# 5

## Human-eye simulation

Visual AI ignores rendering noise like anti-aliasing and sub-pixel shifts, and flags only the differences a real reviewer would notice.

# 6

## Root cause analysis

See the exact screen, element, and region behind a failure, so you can tell a real bug from a device rendering quirk.

## Catch the bug before your customers find it on their device