xUI Installation & Deployment Guide
Use this guide to add xUI to ArcGIS Experience Builder Developer Edition, confirm that it works, and prepare an xUI-enabled application for production.
xUI licensing
You may download and use xUI for development and evaluation at no charge. A purchased xUI license is required before deploying xUI in a production environment or making an xUI-enabled application available to end users.
Request a license
Request a license
1. Before you begin
You will need:
- ArcGIS Experience Builder Developer Edition already installed and running.
- The Experience Builder version number, such as 1.21.
- Permission to copy files into the Developer Edition installation.
- A purchased xUI license before any production deployment.
Version compatibility matters:
Download the xUI package built for your exact Experience Builder Developer Edition version. For example, use the EXB 1.21 package only with Developer Edition 1.21.
2. Download the correct xUI package
- Return to the xUI Downloads page.
- Expand the row matching your Experience Builder Developer Edition version.
- Choose the recommended xUI release unless you need a specific earlier version.
- Select Download ZIP.
- When the download finishes, locate the ZIP in your browser's Downloads folder.
A filename such as XUI-v0.7.1-exb21-dev.zip identifies xUI 0.7.1 built for Experience Builder 1.21.
3. Install xUI in Developer Edition
- Stop the Experience Builder client if it is currently running. In its command window, press
Ctrl+C. - Open the downloaded ZIP and extract its contents to a temporary folder.
- Locate the extracted
XUIwidget folder. This is a compiled, obfuscated distribution; it should containdist,config.json,icon.svg, andmanifest.json. - Open your Experience Builder Developer Edition installation folder.
- Browse to:
ExperienceBuilder\client\your-extensions\widgets\
- Copy the complete extracted
XUIfolder into thewidgetsfolder. Do not copy only the files inside it. - Confirm that the resulting structure resembles:
ExperienceBuilder
└─ client
└─ your-extensions
└─ widgets
└─ XUI
├─ dist
├─ config.json
├─ icon.svg
└─ manifest.json
Precompiled and obfuscated package
The Developer Edition download contains the deployable xUI files, not the original source code. Do not rename, rearrange, or edit files inside
dist. Copy the package exactly as provided.
Avoid an extra folder level
If you see a path such as
widgets\XUI\XUI\manifest.json, move the inner XUI folder up one level. The correct path is widgets\XUI\manifest.json.
- Restart the Experience Builder client using the normal command for your Developer Edition version.
- Wait until the client finishes compiling and displays no xUI-related errors.
- Start or confirm the Experience Builder server, then open the Developer Edition home page in your browser.
4. Add and test xUI
- Open an existing experience or create a test experience.
- In the builder, open the Insert widget panel.
- Find xUI under the custom widgets section.
- Drag xUI onto the page and complete its configuration.
- Preview the experience and test the workflows that matter to your organization.
- Check the client command window and browser console for errors before proceeding.
Development and evaluation can stop here and do not require a paid xUI license.
5. Prepare for production deployment
Purchase the xUI license before this step
A production deployment includes making an xUI-enabled application available to internal staff, clients, customers, or the public.
Request a license
Request a license
- Confirm that your organization has purchased the appropriate xUI production license.
- In Experience Builder Developer Edition, open the completed experience.
- Publish the experience.
- From the experience gallery, open the experience's three-dot menu and select Download.
- Extract the downloaded application ZIP.
- Copy the extracted application folder to your supported web server.
- If the application accesses private ArcGIS content, register the application in ArcGIS Online or ArcGIS Enterprise and add the resulting App ID to the application's
config.json. - Open the deployed application's
index.htmladdress and complete a production acceptance test.
For Esri's current application-hosting procedure, see Experience deployment in the ArcGIS Experience Builder documentation.
6. Update an existing xUI installation
- Back up the existing xUI widget folder and any application configuration you need to preserve.
- Confirm that the replacement package supports your exact Experience Builder version.
- Stop the Experience Builder client.
- Replace the existing xUI widget folder with the newly downloaded version.
- Restart the client and confirm that it compiles without errors.
- Open a copy of an existing experience and test it before updating production.
- Re-publish, download, and redeploy the application using your normal release process.
Do not overwrite production without a rollback copy
Retain the previously deployed application until the new release has passed acceptance testing.
7. Troubleshooting
xUI does not appear in the widget list
- Confirm that the package matches your Experience Builder version.
- Confirm the widget folder is under
client\your-extensions\widgets. - Check for an accidental duplicate folder level.
- Restart the Experience Builder client after copying the files.
- Review the client command window for compilation errors.
The widget appears but produces errors
- Confirm you did not mix files from two xUI releases.
- Remove the xUI folder, extract a fresh copy of the ZIP, and reinstall it.
- Test xUI in a new blank experience to separate installation issues from an existing app configuration.
The deployed application cannot access private content
Confirm that the downloaded application was registered in the correct ArcGIS Online organization or ArcGIS Enterprise portal and that its App ID was added to the deployed application's configuration.
Deployment checklist
- Correct Experience Builder package selected
- xUI installed and compiled without errors
- xUI tested in Preview
- Production xUI license purchased
- Experience published and downloaded
- Private-content App ID configured, if applicable
- Production acceptance test completed
- Previous production version retained for rollback