Build & ship

Ship to TestFlight, Google Play and the Amazon Appstore from one command.

vibeview submit sends a signed production build to TestFlight, a Google Play track or Amazon Appstore review, from any computer. For TestFlight it then follows the build through Apple's processing and Beta App Review until your testers have it.

vibeview submit --platform ios --latest --group "QA team" --wait-distribution

Start free Read the docs

Show the prompt

Install the VibeView CLI (npm install -g vibeview) and sign in with `vibeview login`. In this project, run `vibeview submit --check --platform ios` to confirm App Store Connect knows the app, then ask me which of the TestFlight groups it lists to use and send my latest succeeded production iOS build there with `vibeview submit --platform ios --latest --group "<group>" --wait-distribution`. Tell me when testers have it, or what Apple needs from me.

The Store submissions card of a build: a TestFlight submission uploaded to App Store Connect, then processing, export compliance, What to Test, internal groups, Beta App Review and external groups all done, marked Available to testers

Sends to

TestFlight
Google Play
Amazon Appstore

One command, three stores

TestFlight for iOS and tvOS builds; a Google Play track or the Amazon Appstore for Android and Android TV. The dashboard's Submit button on the build does the same.

It follows TestFlight to your testers

After the upload it follows Apple's processing, export compliance, your groups and Beta App Review, and says what to fix when Apple needs something.

Check before you build

vibeview submit --check asks the store whether it knows the app, so a missing app record shows up before the production build, not after it.

Or let the build submit itself

Add --auto-submit to a production cloud build and it goes to the store as soon as it succeeds, even after you close your laptop.

TestFlight

Pick testers, write What to Test, send.

Choose internal and external tester groups for the build
What to Test notes by language; external groups go through Apple’s Beta App Review first
Export compliance can be answered from the app’s Info.plist

vibeview submit --platform ios --latest --group "QA team"

The Send to TestFlight dialog for a Kitlist build: internal and external tester groups, What to Test notes in English and German

Google Play

Every step of the release, on the build page.

Uploads to a Google Play track: internal, alpha, beta or production
Release notes go with it, by language
The build page shows each step and links to Play Console

vibeview submit --platform android --latest --track internal

The Store submissions card of a Kitlist Android build: uploaded to Google Play, release notes and internal testing done

How it works

01
Add your store key

An App Store Connect API key for TestFlight, a Google Play service account key or an Amazon Appstore key, on the Builds page's Stores tab or from the CLI.
```
vibeview credentials play-key add --file service-account.json
```
02
Check the store knows the app

Each store needs the app created once in its own console. Ask before you build; inside a linked project you can leave out the identifier.
```
vibeview submit --check --platform ios --bundle-id io.example.app
```
03
Build it signed

A production cloud build makes the signed .ipa, .aab or .apk, with credentials you uploaded or VibeView generated.
```
vibeview build --cloud --production
```
04
Submit and follow it

Name the TestFlight groups, or the Play track and release notes. The CLI follows the submission, and the build's page shows each step.
```
vibeview submit --platform ios --latest --group "QA team" --wait-distribution
```

Use it for

Upload to TestFlight without a Mac From Windows or Linux: build, sign and send an iOS app to your testers. Staged rollouts on Google Play Release to a share of users first, with release notes in every language. Fire TV apps on the Amazon Appstore Build an .apk and send it for Amazon review from the CLI.

Frequently asked questions

What stays in App Store Connect and Play Console?

App Store review, store listings and screenshots. VibeView uploads the build and sends it to your TestFlight groups or a Play track; on the Amazon Appstore it also sends the version for Amazon review.

Can I submit a Roku channel?

No. Roku channels are published from Roku's own dashboard. Submission covers iOS, tvOS, Android and Android TV builds.

Who on my team can submit?

Admins and developers, the same people who can start cloud builds. Viewers can watch submissions but not send them.

Send your next build to testers

Start free, build in the cloud and submit from the same CLI.