Skip to main content
Momentic supports local and remote Android emulators. Real devices are not supported. Local emulators use your Android Studio install; remote emulators run from any host.

​
Set up with AI

Using a coding agent? Copy this prompt and paste it into Claude Code, Cursor, Codex, Copilot, or any other agent. It runs the wizard with an API key, because an agent cannot complete the browser sign-in, then writes your first test.

​
Prerequisites

The wizard and the manual setup both need:
  • Node.js 22.12.0+ or 24.0.0+ (node -v)
  • A package.json in your project. Run npm init -y if you do not have one. Commit it with the lockfile, so CI and local runs use the same Momentic version.
  • A Momentic account. Sign up to create one.
Android also needs the Android SDK platform-tools (adb), with ANDROID_HOME set to the SDK directory that contains platform-tools/adb. Remote emulators connect through a local adb tunnel, so you need adb even when no emulator runs on your machine. The platform-tools alone are enough; you do not need Android Studio for this. See Install adb.
The manual setup also needs an APK. See Android app setup. To build the APK or to use a local emulator, you also need Java JDK 24+ and Android Studio with the emulator components. The wizard uses a remote emulator, so its sample run needs no local Java, Android Studio, or APK.

​
Set up with the wizard

Run the wizard in your terminal:
It signs you in through the browser, installs momentic-mobile, writes momentic.config.yaml and a sample test under android/, runs the sample test on a remote emulator, and asks which coding agents to set up.

​
Manual setup

1

Install

The examples below use npx. With pnpm, use pnpm exec momentic-mobile; with yarn, use yarn momentic-mobile.
2

Authenticate

Sign in with your browser:
The CLI saves the credentials to ~/.momentic/auth.json and uses them when MOMENTIC_API_KEY is not set.In CI, or in a shell without a browser, use an API key instead. Create one in the dashboard and export it:
Check which account and organization the CLI uses:
3

Initialize

This writes momentic.config.yaml to your project root. In an interactive terminal, it also offers to install the coding agent skills and the MCP server. init --yes accepts the defaults without prompts, so it works in agent shells and CI.init does not create tests. You write your first one in the editor below. For a sample test, use the wizard above instead.
4

Connect your coding agent (optional)

Skip this step if init already did it. The two commands are independent: skills are local instruction files, the MCP server is a live process that gives the agent a device and Momentic tools.
Both commands detect the coding agents on your machine and ask which ones to configure. Pass --yes to skip the prompt. See Building with AI for what each one does.
5

Build your app

Momentic installs an .apk. Build it with the tab that matches your stack. See Android app setup for full instructions.
If your app shows content in an Android WebView, enable WebView debugging so Momentic can attach: WebView.setWebContentsDebuggingEnabled(true). See Android app setup for details.
6

Upload your APK (remote emulators)

Remote emulators are the fastest way to start. They need no local emulator image or Android Studio. Upload your APK to a channel:
For local emulators, see Android emulators for the LOCAL_AVD_ID and LOCAL_APK_PATH setup.
7

Write and run your first test

Open the local editor:
You write mobile tests in this local editor, not in the web app. The dashboard at app.momentic.ai shows results. A browser-based editor for mobile tests is not available yet.
Create a test, select the dev channel and the 1.0.0 tag, and write one natural-language step, for example Tap the Sign in button. Save the test. The editor writes the .test.yaml file to your project. Run it from the editor, then run it from the CLI by name:
--upload-results sends the result to the dashboard. Without it, the run stays on your machine.
8

Verify

  • Check that the .test.yaml file exists in your project.
  • Open the dashboard and check Runs for the result.

​
Next steps

Android app setup

WebView debugging, APK packaging, environment tooling

Emulators

Local vs. remote emulators and regions

Building with AI

Skills, the MCP server, and a prompt for your coding agent

CI/CD

Run mobile tests on every pull request
Clone momentic-ai/examples for a full working example.