Quickstart: your first build

BuildStack builds and signs your mobile apps in the cloud, so you don't maintain an Android SDK, a Mac, or signing machinery yourself. This walks you from zero to a signed build.

1. Create a project

A project is one app. Open Projects → New project, give it a name and the app's package name (for example com.acme.app).

2. Get your source to BuildStack

Two ways:

• Connect a GitHub repo (recommended): builds run automatically on every

push. See Connect your GitHub repo.

• Upload a source archive: a one-off .tgz of your project, straight from

the dashboard or the dbs CLI.

3. Add signing (once)

• Android: upload a keystore, or let BuildStack generate and manage one for

you. See Android signing & keystores.

• iOS: add your App Store Connect API key (.p8). See Apple credentials.

You only do this once per project; credentials are sealed and reused.

4. Build

Open the project and go to the Build tab. Pick the platform, then a build type (Android):

• Development: a debug APK for use with a Metro dev server (won't run

standalone).

• Preview: an installable release APK with the JavaScript bundled in; runs

standalone on any device. No keystore needed, best for scan-to-install testing.

• Production: a signed release (APK or AAB) for the Play Store; needs your

keystore.

For iOS, choose the scheme, configuration, and export method instead — and optionally a submit target (TestFlight / App Store). See Build an iOS app.

Optionally set a Version name / code (Versioning), then start the build. BuildStack runs it on managed compute and hands you the artefact when done.

5. Ship it

• Android → Google Play: turn on Publish to Google Play on a Production

build; see Publish to Google Play.

• Send to your own testers: share an install link/QR via

channels.

What's next

• Wire builds into your pipeline with the API keys & the `dbs` CLI.
• Run your existing GitHub Actions on BuildStack compute; see

Run CI on BuildStack.

• Understand the moving parts in How BuildStack works.