Beyond Web AppBuilder: A New Experience in App Building

As we move closer to the retirement of ArcGIS Web AppBuilder in Q4 2025, it's crucial to explore the future of app building within the ArcGIS Online ecosystem. While Web AppBuilder has been a reliable tool for years, it's time to embrace the next generation of app creation: ArcGIS Experience Builder.

ArcGIS Experience Builder is a versatile platform for creating highly customized and interactive web apps. However, its extensive customization options can sometimes overwhelm users who want to build a functional app without delving into the technicalities.

To bridge this gap, Esri has introduced Express Mode, a streamlined version of Experience Builder that offers a more structured, template-based approach to app creation. Reminiscent of ArcGIS Web AppBuilder, this model is perfect for users who want to quickly build visually appealing apps without extensive coding or design knowledge.

But how does ArcGIS Experience Builder compare to Web AppBuilder?

To find out, we'll conduct a hands-on comparison. We'll build the same app using all three tools, highlighting their differences. By the end, you'll understand which tool best fits your next project and GIS goals.

Let's get started!

Web AppBuilder

In a matter of a few minutes, I built a simple application that allows users to learn more about waterfalls in the city of Hamilton with data from Hamilton’s open data hub. Using the Billboard Theme, I added five widgets: about, basemap gallery, filter, draw and print.

Billboard Theme Web AppBuilder application for waterfalls in Hamilton

Those familiar with Web AppBuilder know this process is quick and easy. Five slots are available and you can fill each with a widget from the bank of options. Each widget is configured directly after it is added and you can go back and make changes through the widget menu if needed. The application is automatically responsive to alternative device screens without additional configuration.

While easy to use, it is a rigid application; you cannot add more than five widgets and the only UI changes you can implement are to the colours of the widgets and which of the four predetermined locations you want them aligned:

ArcGIS Web AppBuilder has limited options for app configuration

As it is retiring, we are using this version of the application as our baseline and will use Experience Builder in both express and full mode to make duplicates of this app. 

ArcGIS Experience Builder – Express Mode

Like with Web AppBuilder, I produced a nearly identical application using Experience Builder express mode in only a few minutes. The same billboard template was available and with just one different widget, I created the same user experience:

Billboard template ArcGIS Experience Builder application for waterfalls in Hamilton built in express mode 

All but the box theme from Web AppBuilder have been replicated in the Experience Builder Templates, making the duplication process very straightforward. The critical difference is how you interact with the widgets to add them. In Web AppBuilder, we select the empty widget placeholder through the docked widget tab to the left of the map; however, in Experience Builder express mode, all our actions are driven by the application itself. Selecting the widget controller on the map shows us the buttons to add, remove or manage our widgets.

The option to manage and add widgets appears after selecting the widget controller on the map

Once the widgets I want for this app are added, they are individually configured by selecting them in the widget controller and using the setting on the right side of the map:

Selecting a widget inside of the application opens the configuration options to the left of the map

The configuration of individual widgets in Experience Builder can be more complex than in Web AppBuilder. There tend to be more options, and in some cases, like with the filter widget, you need to connect to the data before you can begin configuring. This experience is the same in the full mode of Experience Builder and it just takes some time working with the options to become familiar with the process. 

At this point, my app looks and works the same way as the original created in Web AppBuilder; though with Experience Builder, I can take it further. There is no hard limit on the widgets I can add and if I want to include additional widgets in my controller, that is an option. I can also enable the sidebar to allow users to see the tabular data for my feature.

More than five widgets can be added to the widget controller. This application has been enhanced by adding the directions and edit the widgets.

In only about 15 minutes, I can set up and run an application that is not only the same as the one built-in Web AppBuilder but also has additional features. If I want to take this app even further, I can convert it to full mode, with a warning that if I do, there is no going back!

You can convert an existing express mode application to full mode, but it is a one-way conversion. If you are not ready to make that change, try saving it as a copy instead.

We have what we need from our app and will not convert, but let’s once again build this same app from scratch, this time with Experience Builder in full mode.

ArcGIS Experience Builder – Full Mode

Starting up with Experience Builder in full mode is immediately more complex. Instead of the nine templates available in express mode, there are over 50 to choose from, including three that are completely blank. I am keeping it simple and using the billboard template again.

The option to add, delete, and manage widgets is no longer docked at the top of the application

The two most significant differences you can see with full mode are the options above the application, including locking the layout and live view buttons, and the left side toolbar. In full mode, all the widgets in the application can be moved freely, so you may need to lock or unlock the layout as you make changes. Unless Live view is enabled, you cannot interact with the contents of the application, i.e. panning the map and enabling filters; you are only configuring features.  

Having a flexible layout means you often need to lock or unlock things when making changes and testing features

On the left side the toolbar, we now see options including Insert Widgets and Page. These sections enable us to add widgets outside of the controller and completely change the configuration of our page designing fully custom apps. It is important to be aware that because of this extra functionality, the process of resizing the application can change and you will likely need to make individual changes to the mobile and tablet layouts to optimize the user experience. For the application we are making today, we can skip these features but can follow along with the Get Started with ArcGIS Experience Builder tutorial to get hands-on experience.

(left) The insert widget tab allows you to add any widget to the application outside of the widget controller. (right) the page tab helps to manage the elements of the application 

In the full mode of Experience Builder, even customizing the look and feel of widgets can go further. I was able to change the shape of the widgets in my widget controller from circles to squares to better match what I created with Web AppBuilder. You can see in my final application that it is nearly identical to the first app I made.

Billboard template ArcGIS Experience Builder application for waterfalls in Hamilton built in full mode

With only a few extra minutes of work, I created an application that appears closer to original goal. However, since I have worked with Experience Builder in the past and am familiar with the widget configuration process, I would expect it to take longer for a new user to create the same app. If you see yourself building more complex applications in the future, it may be worth skipping express mode and starting your learning in the full version of Experience Builder. The steps to create the same application can take more time, but you will become familiar with the intricacies of Experience Builder when you start creating those more complicated apps.

Final thoughts

ArcGIS Experience Builder’s express mode is very similar to ArcGIS Web AppBuilder. With rigid templates and always being in ‘live view’ while working, the experience has been replicated well while maintaining the more advanced options in Experience Builder. For users who have not yet moved away from Web AppBuilder, this is the perfect tool to ease yourself into the more complex features of Experience Builder. By making it accessible to use, we also see that it is limited. It will be up to your unique needs and experience to determine which version works for your projects. Check out the table below for a direct comparison between the express and full mode of Experience Builder.

The Future of App Building

As we move forward, it's clear that ArcGIS Experience Builder, with its powerful features and user-friendly Express Mode, is poised to become a go-to tool for building web apps in ArcGIS Online. By understanding the strengths and limitations of each mode, you can choose the best approach for your specific needs. It is important to note that ArcGIS Experience Builder is not the only option when looking for a replacement for Web AppBuilder. To learn more about the other app builders and get guidance on when each is right for your project, check out my colleague Alex Moore’s blog series “A GIS App for Every Need - Part 1 and Part 2” where he will help you navigate this often-complex decision.