> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/frequently-asked-questions/publishing-and-distribution/user-impact-after-replacing-app.md).

# User impact after replacing app

### What happens to existing app users after replacing your live app with an AppMySite-built app?

Replacing your live app with the one you create on AppMySite ensures a seamless transition for your app users. They can simply update the app from the Google Play Store or Apple App Store to access the new version.

* Your AppMySite app will replace the existing app on the app stores, making it available for users to update at the click of a button.
* Once updated, users will experience the new version of your app without requiring a fresh installation.
* No user data will be lost in the process, ensuring a smooth upgrade experience.

{% hint style="danger" %}
Turn the toggle on for Force app update from the [**Settings**](https://docs.appmysite.com/) screen in your account. This will display a prompt to your app users to update the app when you release a new version on the app stores.
{% endhint %}

{% hint style="warning" %}
Users can update their app directly from app stores and access the new version without reinstalling it.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmysite.com/frequently-asked-questions/publishing-and-distribution/user-impact-after-replacing-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
