A generation pipeline
Every change is type-checked, linted, bundled with Metro and driven in a browser at phone size before you see it.
Expo · EAS Build · EAS Update
Sorvel generates Expo apps and drives Expo's own tools for you: the QR code for Expo Go, a development build when native modules need one, EAS Build for the stores, EAS Update for fixes after launch. On your Expo account, in panels instead of a terminal.
| Expo tool | What it does | In Sorvel |
|---|---|---|
| Expo Go | Runs a project on a phone without building it | Open on phone panel: QR code, the matching Expo Go build linked |
| Development build | Your own app binary that loads code changes live | Built once from the Publish panel; the device panel asks for it when needed |
| EAS Build | Store binaries in Expo's cloud | Build app (EAS) in the Publish panel, status shown live |
| Store submission | Getting builds into the stores | Send to Google Play after the first manual upload; a step-by-step App Store submission guide |
| EAS Update | Over-the-air JavaScript updates | Releases panel: channels, mandatory updates, rollback, native-change check |
| expo.dev account | Owns builds and updates | Your access token, connected once in Settings → Integrations |
Every change is type-checked, linted, bundled with Metro and driven in a browser at phone size before you see it.
Navigation, forms, lists, charts, sheets and theming that every generated screen uses, so apps stay consistent.
Notifications, purchases, ads, Sign in with Google, deep links and Sentry, each with its keys and a guide.
The desktop app builds Android (and iOS on a Mac) on your own machine, with no Expo account and no queue.
Your own project, with schema SQL and row-level security generated from the app's data model.
One Git commit per generation; roll back from History if a change goes wrong.
Yes, for cloud work: connect an access token from expo.dev once under Settings → Integrations, and EAS builds and EAS updates run on your account. The desktop app can also build locally with no Expo account.
Expo Go is fine until the project uses a native module it does not carry; then the Open on phone panel steers you to a development build, which you build once from the Publish panel. On iPhone, Expo Go from the App Store only carries the newest SDK, so the panel offers the browser or a dev build there.
The SDK Sorvel's template is pinned to, so every kit module is known to compile with it. The Open on phone panel links the Expo Go build that matches your project's SDK.
The Releases panel publishes the current state as an update to a channel, shows what is live on each channel, can mark an update mandatory, and rolls back by republishing an earlier release. It checks first whether a change is JavaScript-only, because an update that touches the native side can never arrive.
Yes. The project is a standard Expo app in a Git repository; push it to GitHub or download it and run the Expo CLI and EAS CLI as usual.