Quickstart

This guide takes you from an empty workspace to a running Android device. You need an APK and a browser.

1. Create a workspaceCopy Anchor Link

Sign in at app.spawndroid.io and create an organisation. A workspace holds your artifacts, runners, API keys and members. The Free plan is active immediately and needs no payment details.

2. Upload an APKCopy Anchor Link

From the console, open Artifacts and choose Upload APK. Drag in a universal .apk file or browse for one. Builds up to 512 MB are supported.

To upload from a script or a pipeline instead, post the build with an API key:

curl --request POST https://app.spawndroid.io/api/apps \
  --header "Authorization: Bearer $SPAWNDROID_API_KEY" \
  --form "file=@app-release.apk"

SpawnDroid reads the manifest, extracts the icon and the package name, stores the build, and returns the artifact record.

A dashboard upload boots a device immediately. An upload that authenticates with an API key only stores the build, so a pipeline can push many builds without holding devices open.

3. Watch it runCopy Anchor Link

Open the artifact and the player attaches to a live device. The first boot usually takes well under a minute. Once it is ready you can tap, type and scroll the real app, and the screen updates live.

If you uploaded from the console the device is already booting. If you uploaded from CI or the API, press Stream on the artifact to start a runner.

4. Automate itCopy Anchor Link

When you want automated tests in your pipeline, create an API key under Settings and Billing and continue with the API reference or the CI tests guide.

Next stepsCopy Anchor Link

• Core concepts: what a workspace, artifact and runner mean here.
• Plans and limits: parallel runners, seats and history.
• API reference: the full programmatic surface.