Mobile apps, minus the native project
Lakebed
Native
Write the app. Keep the backend. Skip the Expo project, native folders, Metro configuration, signing boilerplate, and rebuild cycle.
$ npx lakebed-native new my-app
import { Screen, Button }
from "lakebed-native/ui";
export default function App() {
return <Screen title="Today">
<Button>Ship it</Button>
</Screen>
}
TODAY
Field notes
OTA
The difference
React Native is the engine.
Lakebed Native removes the garage.
React Native directly
- 01 Create and maintain an Expo or RN project
- 02 Own ios/, android/, Metro, routing, and config
- 03 Wire backend, auth, database, and transport
- 04 Rebuild native binaries for project changes
- 05 Repeat the setup for every app
Lakebed Native
- 01 Start with app/, server/, and shared/
- 02 Use one universal native shell
- 03 Deploy onto the same Lakebed hosted backend
- 04 Ship UI and logic updates over the air
- 05 Pack a standalone app when it is ready
A tighter loop
From blank folder to running app in three commands.
npx lakebed-native new field-notesScaffold only the capsule code you own.
npx lakebed-native devRun the server and native UI with fast iteration.
npx lakebed-native deployPublish the backend and native bundle together.
Built for momentum
Spend time on the product, not the project around it.
Real React Native components and shell-backed device APIs for notifications, sign-in gates, and files.
Database, auth, server functions, deploys, and domains use Lakebed hosted.
A small, legible capsule surface that coding agents can build and operate reliably.
Inject the capsule bundle into the minimal shell for an installable phone app.
Build the app you meant to build