> 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/publish-changes-to-production.md).

# Publish Changes to Production

Push your saved changes to everyone already using your app.

Publishing pushes your saved changes to every customer using your app. There is no store submission and no review — the update arrives over the air, and customers see it the next time they open the app.

This is how most changes ship. Colours, screens, URLs, navigation bar buttons, hidden elements, custom CSS — all of it reaches customers this way, in minutes.

## Before you publish

**Save first.** Anything still sitting as an unsaved draft will not go out. Each section has its own **Save as draft** button.

**Check it in the preview app.** Saved changes appear in Twinr Preview straight away, on a real phone, before any customer sees them. See [Preview App](https://help.twinr.dev/create-app/preview-app.md).

{% hint style="info" %}
Publishing goes to everyone at once. There is no staged rollout and no per-customer targeting, so the preview app is where you catch mistakes — not production.
{% endhint %}

## Publish

Click the green **send** button at the top of the portal, beside the version dropdown.

A panel opens headed **Update Live App**. Hit **Publish**, and your latest updates go live for your users.

That is the whole flow. There is nothing to fill in and nothing to confirm afterwards.

## What publishing does not cover

Some changes alter the app itself rather than what it displays, and no amount of publishing will deliver them:

* The app's name, icon or launch screen
* App permissions
* Anything your current version's framework does not support

Those need a fresh build submitted to the stores. See [Create New App Version](https://help.twinr.dev/app-version/create-new-app-version.md).

{% hint style="warning" %}
If you have changed your app icon and customers are not seeing it, this is why. Publishing cannot replace an icon — that is part of the installed app, and only a store update can change it.
{% endhint %}

## Who can publish

Publishing to production requires the **App Sessions** add-on, sometimes called PowerSuite. Without it, the publish panel explains the feature and offers **Upgrade Plan** instead of a Publish button.

If you are not the owner of the app, the upgrade button is replaced by a note asking you to contact your app's admin — only an owner can buy it. See [Organization](https://help.twinr.dev/organization/overview.md) for roles.

{% hint style="info" %}
Without the add-on, your changes are not lost. They stay saved against your version and ship with your next store build — you simply cannot push them out on their own.
{% endhint %}

## How soon customers see it

The update is fetched when the app next starts. A customer with your app already open will not see it change under them; they will get it the next time they open it fresh.
