You own the code. Here is how to take it

Every Quiny app is your property from the moment it exists. That is written into our terms, and it is a design decision as much as a legal one. This post is about what that means in practice.

Two ways out

Download the whole thing. Open the code view in your workspace and press download. You get a zip with the complete project. No account is needed to keep it, and you can do this as many times as you like.

Push to your GitHub. Connect your GitHub account, and Quiny creates a private repository under your name and keeps it up to date as it builds. Every version in the console becomes a commit. You can revoke access at any time and the repository stays yours.

Both are free and both are available from the first screen, not just after you have shipped.

What is in the box

A React Native project built with Expo, written in TypeScript. This is the same foundation that companies like Shopify and Discord use for their mobile apps, chosen because it is mainstream, well documented and something any mobile developer can pick up.

Inside it you will find:

• One file per screen, named after your screens: the shop front, the product page, the basket, the checkout, the account.
• Your products, prices and copy in plain data files, using the names you gave them.
• The design tokens from the direction you chose: colors, type and spacing.
• Payment through your own Stripe account. Quiny never sits between you and your money.
• A readme that explains how to run it, written for a developer who has never heard of Quiny.

The database behind the app runs on Supabase, which is Postgres. You can log into it and see your orders and customers in tables.

What it does not contain

Nothing that phones home to Quiny. There is no Quiny runtime, no license check and no dependency on our servers. If we disappeared tomorrow your app would keep working and a developer could keep building it.

Open source components come with their own licenses, and the export lists them. They are the standard, permissive ones you would expect.

Handing it to a developer

Invite them from Settings and they get the repository and the build notes: the eight answers, the design direction, and a plain English log of every step Quiny took. A developer who knows React Native should be productive in the codebase quickly, because there is nothing unusual in it.

You stay in charge of what ships. A developer can change the code, but App Store submissions still go through your approval in the console until you decide otherwise.

Coming back

Taking the code does not close the door. Your workspace keeps its copy, your knowledge tree keeps everything it learned, and you can ask Quiny for changes whenever you like. If a developer has changed the code in the meantime, Quiny reads their changes first and works from there.