Publish to TestFlight and Google Play

Connect a store account to your project and Floot handles the store side of every app build: it signs the build, uploads it, and puts it in front of your testers — TestFlight on iOS, internal testing on Google Play. You need no Mac, no Xcode, and no Android Studio, only the developer accounts.

Start on the Publish screen: open your project on floot.com, click Publish, switch on Publish mobile app, and pick a store under Connect App Stores — or under App stores once the app is live.

Connect Apple

1. 1

   Sign in with your Apple ID

   Enter your Apple ID and password, then the 6-digit code Apple sends to your trusted devices. Floot does not store your password.

2. 2

   Let Floot check the account

   Floot checks that the account is in the Apple Developer Program and has the access it needs to create apps and upload builds. If something is missing, it says what.

3. 3

   Name your app

   On the first publish, choose the App Store name testers and shoppers will see. It has to be unique across the App Store, and Floot checks that it is free. If your Apple account has never published an app, Apple also needs a company name — the seller name shown on the App Store, which cannot be changed later.

4. 4

   Confirm

   Floot creates the app in App Store Connect, checks the bundle ID and signing, and connects the account to the project.

After that, each publish builds the iOS app in about 4 minutes. Apple takes another 5 to 30 minutes to process the build before it appears in TestFlight, and emails your testers an invite.

Connect Google Play

1. 1

   Say whether the app is already on Google Play

   Choose No, it's a new app or Yes, it's already on Play.

2. 2

   Pick the Google account that owns your Play Console

   Sign in with Google, or reuse an account you connected before.

3. 3

   For a new app, create it in Play Console

   Click Create app in Play Console and paste the package name Floot shows you — paste it rather than typing it, since it has to match exactly.

4. 4

   Invite Floot to the app

   Open the app in Play Console, copy the URL from your browser's address bar, paste it into Floot, and click Invite Floot. That gives Floot's publishing account access to this one app, so it can upload builds.

5. 5

   For an existing app, upload your signing key

   Google only accepts updates signed with the key you used before, so upload that keystore (.jks, .keystore, or .p12) with its password. If it holds several keys, pick the one your app is signed with.

After that, each publish builds the Android app in about 2 minutes and puts it on Play Console internal testing.

Every publish after that

• Connected stores get a build whenever you publish with Publish mobile app on. Switch a store off under App stores to skip it for one build.
• Set the version in the Version row before a release (1.0.0 until you change it). The build number is automatic, and Floot keeps it above anything already in the store.
• Every build still comes with the Android APK and the project zip, the same as without a store.
• With a store connected, your assistant can build the app itself when it publishes — just ask for an iOS or Android build.
• A test build goes to the same testing tracks but stops working after 4 hours. Never submit one for review.

Submitting for review

Floot stops at testing. When a build is ready, submit it for review yourself: screenshots, a description, and review notes in App Store Connect, or a store listing and a release in Play Console. Review and approval are between you and Apple or Google, and an app already live in a store keeps its current version until you submit an update.