> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/custom-apps-documentation/get-started/choose-how-to-build-your-custom-app/apps-sdk/manage-testing-and-production-app-versions.md).

# Manage testing and production app versions

When developing an application, to manage the production and test versions:

* the developer writes and tests the code with the test application in Make.
* the developer tracks changes in the local `git` repository, pulling changes from the test application.
* the developer pushes the changes to the production application from the local testing app when they finish the development and testing.

This process improves the maintenance and stability of the application because the development does not influence the production version of the application. In addition, all changes can be tracked in a `git` repository, providing a clear and organized development workflow.

## Prerequisites

To start the development of testing and production app versions, the following is needed:

* The production version of an app in Make. If you already have an app that is in use, use it as the production app.
* The cloned production version in a local workspace. [Clone the app to the local workspace](https://developers.make.com/custom-apps-documentation/get-started/choose-how-to-build-your-custom-app/apps-sdk/local-development-for-apps/clone-make-app-to-local-workspace.md), if you haven't done so already.
* The testing version of an app in Make. Create a new app in Make, with no content, that will function as the testing version of the app. For example, name it `<App Label> Testing`.
* Optional: use version control with Git. To properly track all changes in the local app, it is recommended to use a Git repository, for example, GitHub.

## Development flow

Below is a diagram explaining how a developer can develop testing and production app versions.

<div align="left"><figure><img src="https://1562974717-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNS0mCBwODiYtOVXjc6qf%2Fuploads%2Fgit-blob-5bb500a7b304ca6eb00463d41730e514bb9a65a4%2FFigJam%20basics%20(4).png?alt=media" alt="" width="188"><figcaption></figcaption></figure></div>

## Create a testing version of an app

Connect the testing app with the local app and deploy the current code of the production app to it.

{% stepper %}
{% step %}
[Create a new app origin](https://developers.make.com/custom-apps-documentation/get-started/choose-how-to-build-your-custom-app/apps-sdk/local-development-for-apps/create-a-new-app-origin.md) for the testing app.
{% endstep %}

{% step %}
[Deploy the whole local app](https://developers.make.com/custom-apps-documentation/get-started/choose-how-to-build-your-custom-app/apps-sdk/local-development-for-apps/deploy-changes-from-local-app-to-make-app.md) to the testing app origin.
{% endstep %}
{% endstepper %}

The testing app now contains the same components as the production app.

## Develop the components in the testing app

Now, you can start developing new components or editing the current components in the Testing app in Make, and thoroughly test the app in the Scenario Builder.

## Pull changes from the testing app to the local app

Once you finish the development of new changes and components in the testing app, you can [pull the changes to the local app](https://developers.make.com/custom-apps-documentation/get-started/choose-how-to-build-your-custom-app/apps-sdk/local-development-for-apps/pull-changes-from-make-app.md).

## Deploy the changes from the local app to the production app

To synchronize the changes made to the testing app with the production app, [deploy the changes](https://developers.make.com/custom-apps-documentation/get-started/choose-how-to-build-your-custom-app/apps-sdk/local-development-for-apps/deploy-changes-from-local-app-to-make-app.md) to the production app origin.


---

# 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://developers.make.com/custom-apps-documentation/get-started/choose-how-to-build-your-custom-app/apps-sdk/manage-testing-and-production-app-versions.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.
