> 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/create-new-app-version.md).

# Create New App Version

Start a fresh version when your current one can't use a feature you need.

A new app version is a fresh build of your app, created so it can pick up features your current version cannot use. You submit it to the App Store and Google Play like any other release.

Most of the time you will not need one. Twinr delivers changes over the air, so your app keeps improving without new store submissions — see [Publish Changes to Production](https://help.twinr.dev/app-version/publish-changes-to-production.md).

## When you need one

**Twinr tells you.** Some features only work on newer builds. When you try to use one, the portal says *Current version of your application doesn't support this feature. Please create a new version to use this feature* and offers **Create New**. The [Native Link Sharing](https://help.twinr.dev/navigation-bar-buttons/native-link-sharing.md) and Native Notification Screen buttons are two that do this.

**You are changing what the app is.** A new name, icon, launch screen or set of permissions is baked into the installed app. Only a store update replaces it.

**You want to ship a store update anyway.** Every submission to Apple or Google needs its own version number.

## Create it

Open the **version dropdown** at the top of the portal — the one showing your current version, such as `1.0.7` — and choose **Add New Version**.

Enter your **App version number** and click **Add**.

### Version number rules

The portal checks what you type:

* **Numbers and dots only.** *Only numbers and `.` are allowed.*
* **Must start and end with a number.** `1.0.8` is fine; `1.0.` is not.
* It cannot be blank.

Convention is three numbers — `1.0.8`, `1.1.0`, `2.0.0`. Increase the last number for a small update, the middle for new features, the first for a major release.

{% hint style="info" %}
Use a number higher than the one currently in the stores. Apple and Google both reject a build whose version is not greater than the last one you shipped.
{% endhint %}

## What carries over

**Everything.** Your screens, theme, branding, settings and integrations all come across to the new version. You are not rebuilding your app — you are giving it a newer foundation.

Once created, the new version becomes what you are editing, and the dropdown lets you move between versions.

{% hint style="warning" %}
Save before you switch versions. Moving to a different version with unsaved work loses it, and the portal warns you: *This version has few unsaved changes. Changing the app version without saving it will result in data loss.*
{% endhint %}

## After creating one

A new version is a build to submit, not a change customers receive. Nothing reaches them until you build it and ship it through the stores:

* [Publishing to the Google Play Store](https://help.twinr.dev/app-publishing/publishing-to-the-google-play-store.md)
* [Publishing to the Apple App Store](https://help.twinr.dev/app-publishing/publishing-to-the-apple-app-store.md)

Until that build is approved and live, your customers stay on the version they have.

{% hint style="info" %}
Very occasionally, creating a new version stops you editing an older one — this happens only when Twinr's framework no longer supports a configuration that old, and it is rare.
{% endhint %}
