Orbit builds a native Android version of your app on its servers. The Android app uses the same data and logic as the web app.
Test builds use Sandbox
The Orbit mobile app overview describes the entry point: App settings, then Mobile, then Build test app. You do not need to install Android Studio.
Orbit says a test build takes about 15 minutes. You can close the window while the build runs. The build step shows the result when the build is ready.
The test app uses Sandbox. This keeps test data out of your live app. Shared data and logic do not mean a Sandbox test writes to Production.
For example, a repair business can test a customer request on an Android phone. The repair business is an example, not a built-in app type. A request created in the test app checks the Sandbox version, not the live customer's request history.
A build result is not a completed app test
After you install the test app, check sign-in, the main screens, and saved data. For the repair app example, submit a test request, close the app, then reopen the app. Confirm that the request remains available to the test account.
Check private access with a second account. A successful sign-in does not prove that each customer can read only their own requests. See Authentication for that distinction.
Use Review an app before launch to check the customer's complete task. A successful build alone does not prove that the task works.
Google Play has a separate first release
The mobile app overview says Studio guides you through Google Play after the test. Google requires the first release of a new app through Play Console, so you upload that release manually. Later releases go to Google Play from Studio.
Creating a test build does not publish your app on Google Play. Keep the phone test separate from the store release.
Android builds and home screen installation differ
The native build described here is Android only. An iPhone user can open your app from its web link instead.
An installable web app gives people a home screen shortcut without a store release. That installation does not create a native Android build or a native iOS build.
Choose the web link when people need browser access. Choose a native Android build when you need the Android release path. In either case, check the customer's main task and access to private records.