> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/app-version/overview.md).

# Overview

How your changes reach customers — over the air, or as a new store version.

Everything you change in the portal — a colour, a screen, a new button — is held as a draft until you decide to send it out. **App Version** is where you decide.

There are two ways your work reaches customers, and knowing which one you need saves a great deal of waiting.

## Two ways to ship

**Publish to production** pushes your changes to everyone already using your app. No app store, no review, no waiting — customers get the update the next time they open the app. Most changes work this way.

**A new app version** is a fresh build you submit to the App Store and Google Play. It takes days rather than minutes, because Apple and Google review it. You only need one occasionally.

{% hint style="info" %}
The portal's version dropdown — the one showing `1.0.7` at the top of the screen — is how you move between versions. The green button beside it is how you publish.
{% endhint %}

## Which one do I need?

| What you changed                               | What to do            |
| ---------------------------------------------- | --------------------- |
| Colours, fonts, theme                          | Publish to production |
| Screen content, URLs, navigation bar buttons   | Publish to production |
| Adding, hiding or reordering screens           | Publish to production |
| Hide Elements, custom CSS or scripts           | Publish to production |
| App name, icon or launch screen                | New app version       |
| App permissions                                | New app version       |
| A feature your current version doesn't support | New app version       |

The rule of thumb: **what the app shows** can be published over the air. **What the app is** — its name, icon, permissions, and the framework underneath — needs a new build.

## Pages

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Publish Changes to Production</strong></td><td>Push your saved changes to everyone using your app.</td><td><a href="https://help.twinr.dev/app-version/publish-changes-to-production.md">Publish Changes to Production</a></td></tr><tr><td><strong>Create New App Version</strong></td><td>Start a fresh version to pick up features your current one can't use.</td><td><a href="https://help.twinr.dev/app-version/create-new-app-version.md">Create New App Version</a></td></tr></tbody></table>

## Draft, saved, published

Three states, and it is worth keeping them straight:

1. **Draft** — you have changed something but not clicked **Save as draft**. Nothing is stored yet.
2. **Saved** — your change is kept against this version, and you can see it in the preview app. Customers do not have it.
3. **Published** — your change is live for everyone.

{% hint style="warning" %}
Switching versions in the dropdown with unsaved changes loses them. The portal warns you first: *This version has few unsaved changes. Changing the app version without saving it will result in data loss.* Save before you switch.
{% endhint %}
