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.

​
Prerequisites

The wizard and manual setup both require:
  • Node.js 22.12.0+ in the 22.x line, 24.x, or 26.x. See the Node.js release list for supported release lines.
  • A package.json in your project (run npm init -y if you don’t have one)
  • A Momentic account; sign up to generate an API key
  • Android SDK platform-tools (adb), with ANDROID_HOME exported and pointing at the SDK directory that contains platform-tools/adb. Remote emulators are driven through a local adb tunnel, so this is required even when no emulator runs on your machine. Installing only the platform-tools is enough; Android Studio is not. See Install adb.
Manual setup also requires an APK. See Android app setup. Building the APK or using a local emulator additionally requires Java JDK 24+ and Android Studio with emulator components. The recommended wizard path uses a remote emulator, so it needs no local Java, Android Studio, or APK for its sample run.
Run the onboarding wizard in your terminal. It signs you in through the browser, installs Momentic, runs a sample test against a remote emulator, and sets up the editor MCP server.

​
Setup with coding agent

A coding agent can’t complete the browser sign-in, so the agent path uses an API key and runs the wizard non-interactively. Copy the prompt below into Cursor, Claude, or another agent:

Set up Momentic for an Android project end to end via the onboarding wizard, non-interactively.

Open in Cursor

​
Manual setup

Option A: sign in with your browser (recommended):
This opens a browser-based login flow and saves credentials to ~/.momentic/auth.json. The CLI automatically uses this file when MOMENTIC_API_KEY is not set. Option B: use an API key: Create an API key in the dashboard, then export it:
This writes momentic.config.yaml to your project root. init does not scaffold any tests; author your first one in the editor below. (For pre-scaffolded sample tests, use the onboarding wizard instead.) The wizard configures Momentic’s MCP server and installs agent skills for you. For manual setup, follow the MCP setup guide to connect your editor and install the skills your coding agent needs. Momentic installs an .apk. Build it with the tab that matches your stack. Full instructions are in Android app setup; for more cross-platform detail see Cross-platform.
If your app renders content inside an Android WebView, enable WebView debugging so Momentic can attach: WebView.setWebContentsDebuggingEnabled(true). See Android app setup for details.
Remote emulators are the fastest way to get started, no local emulator image or Android Studio required. Upload your APK to a channel:
Prefer local emulators? See Android emulators for the LOCAL_AVD_ID / LOCAL_APK_PATH setup. Open the local editor:
Mobile tests are authored in this local editor (momentic-mobile app), not in the web app. The cloud dashboard at app.momentic.ai is for viewing results, a browser-based creator for mobile tests isn’t available yet.
Create a test, pick the dev channel and 1.0.0 tag, and author a single natural-language step (for example, Tap the Sign in button). Save it (the editor writes the .test.yaml to your project), run it from the editor to verify, then run it from the CLI by name:
  • Check the .test.yaml you just authored exists in your project root
  • 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

CI/CD

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