One codebase, two stores
iOS and Android from the same TypeScript. The build pipeline and the store guides are part of the product.
React Native · Expo · TypeScript
Describe the app in one message. Sorvel writes an Expo (React Native) app in TypeScript, type-checks, lints and bundles it, drives it in a browser, and runs it on your phone. The repository is yours: push it to GitHub, open it in your editor, ship it with EAS.
No proprietary runtime. A project you could have started with create-expo-app, plus a design kit and a build pipeline.
| Framework | Expo SDK, React Native, TypeScript strict, file-based routing under app/ |
| Screens | Generated under app/: list, detail and form screens, tabs declared in src/tabs.ts |
| Data | Local-first collections in src/store.ts with an offline queue; your Supabase project when connected, realtime included |
| Design kit | src/ui and src/lib: navigation, forms, lists, charts, sheets, theming with curated palettes and dark mode. Locked so a generation cannot break it |
| Native modules | Expo wrappers for notifications, purchases, ads, camera, location, biometrics, calendar, contacts, files |
| Release | EAS Build profiles, EAS Update channels, Sentry crash reporting, store assets and submission guides |
| Repository | Git with a checkpoint per generation; push to GitHub, download a ZIP |
"A field service app with jobs, photos and offline sync." Any language.
Sorvel asks which features and which design direction, then builds exactly that. Sign-in is switched on in the Database panel.
TypeScript strict, ESLint, Metro, then a browser-driven run of the screens. Fixes happen before you see the build.
Scan the QR code with Expo Go or a development build; every accepted change refreshes the app on the device.
iOS and Android from the same TypeScript. The build pipeline and the store guides are part of the product.
Push notifications, in-app purchases, biometrics, camera and location are native modules, not browser APIs in a shell.
Stop using Sorvel tomorrow and the app still builds with the standard Expo toolchain. The code was never hidden.
The generated screens use a locked design kit, so every app ships with consistent navigation, forms, accessibility and theming.
After launch, fixes ship as EAS over-the-air updates from the Releases panel.
Sorvel is an MCP server: Claude Code or Cursor can create and change the same project, with the same checks.
Real React Native. Each project is an Expo SDK app in TypeScript with file-based routing, native modules through Expo's wrappers, and no web view around the screens. You can open it in your editor, run it with Expo yourself, and keep building outside Sorvel.
Whatever the app needs from the kit: push notifications, in-app purchases, ads, Sign in with Google, deep links, camera and barcode scanning, location, biometrics, calendar, contacts, file and image pickers, offline collections with sync, EAS Build and EAS Update. The model is told to use a module only when the app really calls for it.
Yes. Push the repository to GitHub from the Git panel or download a ZIP; it is a normal Expo project. If you keep editing in Sorvel too, the kit folders are locked so the next generation cannot break them, and everything else is yours to change.
Every build is run through the TypeScript compiler in strict mode, ESLint with the kit's rules, the Metro bundler, and a browser-driven run of the app at phone size that opens screens and adds a record. Failures are fixed by the model before the build is accepted; a build that still fails is not charged.
Not to build or preview: the preview runs in Expo Go or a development build on your phone, and store builds run on EAS. The desktop app can also build locally on your own machine if you have the toolchains installed.