Blog · Strategy
Own the code, or rent the app
Every app builder says you own your app. Few mean the thing you mean. Ownership is not a line in the terms; it is whether the app keeps running on a laptop with the vendor’s servers switched off. Here is how to tell renting from owning before you have built anything.
1. The test: unplug the vendor
Imagine the company behind your tool shuts down tonight. Tomorrow morning, does your app still open on your phone? Can a developer you have never met take the code, open it, and make a change?
- If the answer is yes, you own it.
- If the app needs the vendor’s runtime, servers or account to start, you are renting it, however the pricing page is worded.
Most no-code builders fail the test by design: the app is their platform wearing your logo. Some “export code” options fail it too, because what they export needs their runtime to run. Ask for the test, not the promise.
2. What a real export looks like
A real export is a normal project in a mainstream framework, the kind a developer would recognise from any job listing: a React Native project built with Expo, say, with the screens, the navigation and the native configuration in plain files. You can open it, build it, change a label, and publish it with your own developer accounts. Nothing in it phones home, and nothing in it needs a key to keep working.
Two tells of a fake export: the code depends on a private package only the vendor publishes, or the “export” is a design file rather than an app.
3. The perpetuity question
The second question is sharper than the first: what exactly stops when you cancel? There are only two good answers, and one of them is “nothing”. The other is “the updates”, meaning your app keeps working exactly as it is, and you stop receiving the new versions of the parts the vendor supplied when the phones change.
That second answer is honest and fair, because keeping an app current as iOS and Android move is real, ongoing work. Anything beyond it, your app stopping, your export expiring, your screens going dark, is rent. Get the answer in writing, in the terms, and read the terms.
4. Why it matters more now
Phones change every year, and in 2026 they changed a lot: Apple’s iOS 26 look, Google’s Material 3 Expressive, a new requirement from Xcode 27 that crashes unprepared apps at launch on iOS 27. An app you own can be updated by anyone. An app you rent can be updated only by the vendor, on the vendor’s schedule, for as long as the vendor exists.
Ownership is also what makes the AI path work. A coding agent can keep improving an app only if the code is open to it. A locked platform is a dead end for your agent as much as for you.
5. Three questions, before you build
- Can I export a normal project, and in which framework?
- Does the exported app run with your servers switched off?
- What exactly stops when I cancel?
Ask them of any tool, including ours. For the record, the App Builder‘s answers are: a standard Expo project with the screens, navigation and app shell in plain code; yes, nothing in the export calls home; and only the stream of updates to the components and shell we supplied, never the app itself. Designing is free, and an app you have exported works forever.