How to Download Your App's Code and Keep Building It Yourself

Can I download my app's code?

Yes. On a Pro or Studio plan, choose Download .zip in the Studio toolbar (or Options (⋯) → Download .zip on a phone). You get the React Native and Expo project to open in your own editor.

After downloading

1. Read the project's instructions and package manifest, and install with its dependency versions.
2. List which services the app needs and who owns each account.
3. Test sign-in, saved data and provider requests in the new environment.

What a ZIP does not include

A ZIP of app files does not move a database, provider accounts or hosted services. Keep credentials out of client code. Apps that use Supabase and AI connectors together currently need extra connection setup after export; have a developer verify both.

Source export is not publishing

A source download is not a signed build or a store submission.

Think of export as a handover

The source ZIP contains project files, not everything the running product depends on. Before moving work to your own editor, list the backend, file storage, AI providers and build services the app uses.

For each, note the owner, required configuration and how the project connects. Store actual secrets in the appropriate private configuration, not in a public handover document.

Keep an untouched copy

Save the original export with the project name and download date. Work in a separate copy or version-controlled repository. That makes it easier to distinguish an exported issue from a change you made locally.

Inspect the package manifest and lockfile before installing. Use the project's expected runtime and package versions rather than upgrading everything immediately. A dependency upgrade is a separate change to test.

Run the smallest check first

Start the project using its instructions and open a supported preview. Confirm the initial screen and navigation. Then test connected behavior: sign-in, saving and provider requests.

If a service fails, identify whether its configuration is missing, the environment is different or access is denied. Do not solve a permission error by placing a privileged server key inside the mobile client.

Identify platform configuration

The app's bundle identifier, Android package name and signing destination matter when producing new builds. Keep them aligned with the existing store records if you are continuing an already distributed app.

Changing the app's visible name is different from changing its identity. A new identifier can create a separate app rather than update the one users already installed.

Decide where development continues

Downloaded edits do not automatically sync into RNBlocks. Choose a primary working copy and a clear process for future changes. Otherwise you can end up with two versions that each contain fixes missing from the other.

If a developer takes over, provide the task history and known limitations as well as the code. 'Save works locally but needs cloud setup' is useful handover information. A polished screenshot is not a substitute.

Export does not transfer licenses or accounts

Check third-party asset and package terms, and retain records for materials you use. A downloaded project does not automatically transfer ownership of an external provider account, a store membership or hosted data.

Verify the handover with a concrete task

Use the exported project to complete the main journey in the new environment. Reopen saved information and test any required provider calls. Then create the appropriate build if installation is the goal.

A successful download confirms that you received files. A successful handover means those files and the documented dependencies let you continue maintaining the app.

Is a source ZIP an installable app?

No. It is the project used to build the app. Installation requires an appropriate binary and distribution route. Uploading a ZIP of source to a store is not the same as submitting a signed build.

Can I upgrade every dependency immediately?

You can plan upgrades, but first establish a working baseline. Upgrading the runtime, native libraries and app code together makes failures harder to isolate. Keep the lockfile and test meaningful changes.

Will the backend still work?

It depends on the exported configuration and services involved. Check sign-in, data access and external calls in the new environment. A database remaining online does not guarantee the downloaded client has the correct supported connection route.

Can another developer continue the app?

Provide the source, instructions, service ownership information and known limitations. Use appropriate collaborator access rather than pasting broad credentials into a general document. The developer needs context as well as files.

What should I verify before relying on the export?

Run it, complete the main task and check connected features. Keep an untouched copy and a clear primary working version. If you need a store update, confirm app identity and signing before producing the next build. These steps make export a usable continuation path instead of a backup you have never opened.

Questions people also ask

Is the code mine?

You can download your app's source on Pro and Studio plans and keep working on it in your own tools.

Can I come back to RNBlocks after editing locally?

Downloaded edits do not sync back into Studio automatically. Decide where you will continue working.

Which tools do I need locally?

Node.js and the Expo tooling described in the project's instructions. Cloud builds can be made with EAS.

Build it with RNBlocks

RNBlocks lets eligible paid-plan users download the app's React Native and Expo source. Start free to build and refine the journey, then use export when you want to continue in your own tools. Keep the connected-service setup with the project so the handover remains useful.

Choosing an app builder that lets you keep the source code

Code ownership and a usable export are related questions, but check both. You want to know whether you can download the project, what format it uses, which plan includes export and what you need to run it after leaving the builder.

RNBlocks generates React Native and Expo app projects and provides a source-download workflow. Check current pricing for export access. After downloading, keep the ZIP, extract it into its own folder and read the project instructions and dependency files. Those files tell the next developer more than a marketing claim that the code is “yours.”

An export does not include a replacement for every connected service. Your database, model provider and store accounts still have their own configuration, billing and access requirements. Do not put private credentials into a public repository when continuing the project. Configure the supported environment and service connections separately.

If you want to keep building with RNBlocks, you can continue refining the app in the conversation. If you want to continue independently, test the exported project in the required development environment. In either case, downloading source is different from producing a signed build or submitting it for review. Use the publishing guide for those later steps.