Push notifications
Send to every install from the Notifications panel, with a send-to-yourself-first step.
Android · Google Play · APK and AAB
Describe the Android app you want. Sorvel builds it, runs it on your phone while it builds, gives you an APK to share and an AAB for Google Play, and takes you through the Play Console, including the first upload Google insists on doing by hand.
"A gym app with class bookings and a membership card." Pick the features and a design direction.
Expo Go, the browser, or a development build; changes arrive as you ask for them.
An APK to hand to testers, an AAB for the store. In Expo's cloud, or locally in the desktop app.
Google requires the first release by hand in the Play Console; Sorvel hands you the file and the numbered steps.
One click from the Publish panel through your service account, or an over-the-air update from Releases.
| Step | You | Sorvel |
|---|---|---|
| Developer account | Open a Google Play Console account ($25, once) | Explains every field it asks for |
| Build | Nothing | AAB for Play, APK for testers; cloud (EAS) or local in the desktop app |
| First release | Upload the first AAB by hand, as Google requires | Gives you the file and the steps |
| Later releases | Authorize a service account once | Sends each new build to Play with one click |
| Testing | Add testers | Puts the Play internal-test route on store-signed builds |
| Listing | Review and publish | Icons, framed screenshots, listing texts and the privacy page |
Send to every install from the Notifications panel, with a send-to-yourself-first step.
Google Play billing through RevenueCat, and AdMob ads with the declarations Play asks for.
Its own panel: OAuth client ID and the SHA-1 fingerprint, explained in order.
Collections keep working without a network and sync when it returns; realtime when it is on.
App links that open a screen from an https address, with the assetlinks file written for you.
Over-the-air updates for JavaScript changes; the panel says when a native change needs a new build.
An APK installs directly on a phone: the format for testing yourself or sending to a few people. Google Play does not accept it. An AAB (Android App Bundle) is what Play expects, and it cannot be installed on a phone directly. Sorvel builds either.
A Google Play Console developer account, a one-time $25 fee. Google requires the very first release of any app to be uploaded by hand in the Play Console; Sorvel gives you the file and the steps. After that, every update is one click from the Publish panel through a service account you authorize.
Scan the QR code from the Open on phone panel with Expo Go (the panel links the build that matches your project's SDK) or with the phone camera to open it in the browser. For native modules, install a development build once; code changes still arrive instantly after that.
Yes, in the desktop app: the local Android build runs on your own computer with no Expo account and no queue, and produces an APK or an AAB. Cloud builds use EAS and need an Expo access token.
No. Uploads to Google Play go through a service account you create in Google's console and authorize for uploads; your personal Google password is never involved.
Yes. It is an Expo (React Native) project, so the same code builds for the App Store. See the AI iOS app builder page for Apple's side.