# Mobile apps

> Test Android and iOS apps in Arcus by recording or learning their steps on a real device in the cloud or a device connected to your computer.

**Mobile apps** are Android and iOS applications you test on a device. Copilot installs a build of the app on a real device from Testsigma Lab, or launches it on a phone, emulator, or simulator connected to the [Arcus Agent](https://testsigma.com/docs/arcus/v2/get-started/installation/arcus-agent/#connect-a-mobile-device) on your computer, and records each tap as an automated step. The app and its builds live in **Test Assets** > **Apps**, so the first thing a mobile test needs is an app there. See [Apps](https://testsigma.com/docs/arcus/v2/run-tests/apps/). A real iPhone also needs a provisioning profile, which Arcus uses to re-sign the build and WebDriverAgent.

| Page | What it covers |
|---|---|
| [Create mobile test cases](https://testsigma.com/docs/arcus/v2/apps/mobile/create-test-cases/) | Create a test case, pick the app and build, record and check its steps on a device, and run it |
| [iOS signing](https://testsigma.com/docs/arcus/v2/apps/mobile/ios-signing/) | Create the provisioning profile that re-signs iOS builds for real iPhones |
| [Devices and emulators](https://testsigma.com/docs/arcus/v2/apps/mobile/devices-and-emulators/) | Connect a phone, emulator, or simulator to the Arcus Agent and use it for sessions and runs |

A test case has no app type of its own: you choose **Mobile**, the app, and the build when you start a Copilot session, and again in the run configuration that runs it. See [Mobile configurations](https://testsigma.com/docs/arcus/v2/run-tests/run-configurations/#mobile-configurations).
