--- title: "Publish and Deploy your First Application" canonical: "https://help.cartinuum.com/space/WC/4538138682/Publish%20and%20Deploy%20your%20First%20Application" format: markdown --- Creating an application in Experience Builder does not automatically make it available to end users. To publish an application for use outside of the builder environment, you must deploy it. Deployment creates a hosted version of your Experience Builder application that can be accessed independently of the builder session - and is available 24x7. ### Understanding Deployment Managed Experience Builder separates application authoring from application hosting. When you work within Experience Builder, you are editing the application's source configuration. End users do not see these changes immediately. A deployment creates a hosted version of the application that is made available to end users. Changes made within Experience Builder are not visible to end users until a new deployment is performed. ![Simple diagram showing the Build, Deploy, Use phases of Experience Builder](media://8eaa7877-7575-4a55-a33b-31cb9568d2b1) ### Before You Begin Ensure that: - [A builder session is running](https://bgt-innovation.atlassian.net/wiki/spaces/WC/pages/4538204198). - [You have signed in to Experience Builder](https://bgt-innovation.atlassian.net/wiki/spaces/WC/pages/4538269743). - Your application has been saved. ### Step 1 – Open Experience Builder Launch Experience Builder and open the application you wish to publish. Make any required changes and save the application. ### Step 2 - Publish Your Application Before an application can be deployed, it must first be published within Experience Builder. Select **Publish**. This marks your changes as ready for deployment. ### Step 3 – Return to the Control Page Managed Experience Builder deployments are managed through the control page. Return to the browser tab containing the Managed Experience Builder control page. ### Step 4 – Deploy the Application Select **Deploy** **app**. Managed Experience Builder will list all apps that have been published and ready for deployment. Locate the application you wish to deploy. Managed Experience Builder will create a deployment package and deploy it to the hosting platform. ### Step 5 – Wait for Deployment Deployment typically completes within about 60 seconds. During deployment: - Application assets are generated. - Hosting files are updated. - Networking is configured to make it available to users. - Cached content is removed. Once complete, the deployment status will be updated. ### Step 6 – Open the Deployed Application Once deployment is complete, the application will appear in the **Deployed App** List. To access the deployed application, open the application’s action menu and select **Open App**. The application will open in a new browser tab. To copy the URL for your application, select the **Copy URL** icon to copy the deployed application’s URL to your clipboard. This URL can be shared with end users, embedded in other applications, or registered as an app in your ArcGIS portal. Verify that: - The application loads successfully. - Recent changes are visible. - Maps and data load correctly. - Custom widgets behave as expected. ### Updating an Existing Application When changes are made within Experience Builder: 1. Save the application. 2. Publish the application. 3. Return to the control page. 4. Redeploy your application. If a newer published version of the Experience Builder application is available, a yellow dot will be shown next to the application. The **Re-deploy App** option will be available in the action menu. The previously deployed version remains available until the new deployment is completed. ### Deleting an Application Select **Delete App** from the action menu to remove the deployed application from Managed Experience Builder. Deleting a deployment does not remove the underlying Experience Builder application from the builder environment. The application can be updated, published and deployed again in the future if required. ### Builder Sessions and Deployments It is important to understand that builder sessions and deployed applications are independent. Stopping a builder session: - Does not affect deployed applications. - Does not make deployed applications unavailable. - Does not remove deployed content. Deployed applications remain available 24 hours a day regardless of whether a builder session is running. --- ### Common Questions #### Why can't users see my latest changes? Changes made within Experience Builder are only visible inside the builder environment until a deployment is performed. Deploy the application to make the changes available to end users. #### Do I need to keep the builder session running? No. Once deployed, applications continue to operate independently of the builder environment. #### Can I deploy multiple times? Yes. Applications can be redeployed whenever changes are made. ### What's Next? Now that your application has been deployed, you may wish to: - [Configure a custom domain](https://bgt-innovation.atlassian.net/wiki/spaces/WC/pages/4538597411). - [Add custom widgets](https://bgt-innovation.atlassian.net/wiki/spaces/WC/pages/4538073204). - [Share access with other team members](https://bgt-innovation.atlassian.net/wiki/spaces/WC/pages/4538564650). - [Manage deployments and builder sessions](https://bgt-innovation.atlassian.net/wiki/spaces/WC/pages/4538335281).