Short answer: you own the source code of every app built here, and you can export it whenever you like. Our terms say it in one line: you own your prompts and your generated apps, and we claim no ownership of the code or content generated for you. The download is free, sits in your app’s settings, and hands you an ordinary React Native project that runs without us. The rest of this note is what that means in practice, because a lot of builders say “your code” and mean a screenshot.
What ownership covers
- The app: every screen, component and helper written for you, from a template or from your description.
- Your data: it lives in a Supabase project. Once you connect your own, it lives in your account, not ours.
- Your prompts: yours, and we do not train AI models on them or on your apps.
- The open-source packages the app uses stay under their own licences, the same as in any codebase.
What is in the download
Open your app, go to its settings, and under “Your code” press “Download my project”. What arrives is a zip containing a complete Expo project, which is the standard way React Native apps are built:
- The root component and navigation, one file per screen, shared components, and the data, theme and helper code.
- Your icon and splash images, and the native config with your app’s name and identifiers.
- A package list of exactly the dependencies your app imports, with versions pinned and a lockfile, so the install reproduces.
- An environment file with your Supabase URL and public key, and blank lines for anything else the code reads.
- Your database: a full schema dump, plus the server functions we deployed into your project, such as the one that sends push notifications.
- A README that gets a developer running in two commands and says which of the above could not be included, if anything.
The database and server pieces come along whenever we can read your backend. If we cannot, the README says so rather than shipping a project that looks whole and is not. If an app fails our own build check, the export refuses instead of handing you something broken.
How to run it without us
Unzip it, install the packages, and start Expo: two commands, both in the README. That gives a developer the bundler and a web preview straight away. Native builds go through Expo’s usual route: generate the iOS and Android projects and build with Xcode or Android Studio, or build in Expo’s cloud. The README walks through both. The app uses native modules, so it does not run in the Expo Go sandbox, which is normal for a real app.
What is deliberately not in it
Nothing of ours. No platform secrets, no keys to our build pipeline, and none of the machinery that generated the project. What you get is a conventional codebase with no trace of how it was made, which is the point: a developer you hire later opens it and sees a normal Expo app. The small helper files that came from our scaffold are released to you under the MIT licence, so you can keep, change or delete them.
Why this matters when you choose a builder
Some builders never let you leave. Others let you export the source code only on a paid tier, or export something that only runs inside their platform. Ask three questions of any tool: do I own the code, can I export it, and does the export run anywhere. Here the answers are yes, yes and yes, and the export is free on every plan, including for apps built from free templates.
Ownership you cannot download is a promise. Ownership you can unzip is a fact.