We are excited that you’re joining us for this beta release. Before we dive into the details of this beta, we want to provide you with some context on why we are really excited about Experience Builder.
Experience Builder is a unified build system that enables you to deliver modern 2D and 3D web experiences. An “experience” is a web app or web page that may include a page, section, widget, data source, theme, and layout. Although location is at its core design, there are many possibilities of the types of apps you can create with Experience Builder such as:
We have built Experience Builder to provide you with full control of creating the design and workflow for your app. This is possible by using drag-and-drop functionality to position your map, image, menu, and other widgets to build that unique experience for your app.
Now that you know what Experience Builder is about, let’s get into this beta release. Remember, this is a beta release and the features that are in this beta are just a portion of what will be in the final product later this year. So, you might be asking yourself, “What are the expectations of this beta?” Well, we are looking for you to try out the following:
Interface
When you click to create an experience from a template, you will see that the UI is made up of the following:
Header
In the header section, you can do the following:
Page
A page is a document that is the foundation for the layout. It has three components: a header, body, and footer. A layout may contain a single page or multiple pages. The best approach when designing your layout is to put your content first and decide how it needs to be presented to your users. For content focused mainly on the map, we recommend using a full screen app page for this type of web app layout. For content that contains multiple images, text headings, maps, and requires vertical scrolling, the scrolling page layout is best suited for this web page layout.
Pages are listed under the Page tab. This is where you add and switch between pages, remove, duplicate, and rename the pages, while also organizing the pages hierarchically. You have the option to change the default homepage and hide any page from showing in the menu. Additionally, you can add links and folders to your page. Each page has a page setting, and in this panel, you can change the name of the page and select the width of your page to custom or auto. There are also options to select the body fill color, add a header and footer, and add gap and padding to your page.
The UI elements that exist for the current page are listed in the Outline panel. Widgets appear on the page in these three areas: header, body, and footer.
Data
Data is defined using data sources. Widgets can access data from private and public content on ArcGIS Online. This includes web maps, web scenes, feature layers, and URLs.
Theme
A theme defines the typography (e.g., font family and font size) and color for the text and background used in the header, body, and links in the app.
Toolbar
The toolbar provides tools that enable you to do the following:
Canvas
The canvas is where you design and build apps. There are two options to layout the widgets in your app, a full screen app page, and a scrolling page. Widgets are added to the canvas by dragging-and-dropping. There are red guidelines to help you position a widget with reference to other widgets on the canvas.
Widgets
Widgets are the building blocks of your apps. To add a widget, click and hold to drag the widget to the desired placement on the canvas. Widgets are configured on the right-side panel under Content, Style, and Action. Content defines the behavior, data, and other settings for the specific widget. Each widget has unique configurations, which we will illustrate below. Widgets are aligned and styled in the Style tab with settings including position, layout, background, border, border-radius, and box-shadow.
The size and position properties define how the widget is positioned on the page by width, height, and location. You can specify these values in pixels (px) or percent (%) to determine how your content is displayed. In addition, you can use the auto value as the default for these properties. Borders can be dashed, dotted, double, or solid with your color of choice and size. There are options to add corners to your widgets using border-radius and incorporate box shadows using properties, such as spread and blur radius. Widgets such as Map and List have the ability to add a trigger under the Action panel. For example, in the List widget, you can add an action such as pan to the map once a feature is selected in the list.
In the Widgets panel, there is a tab called Pending. This feature is very useful when you need to design your app for multiple screen sizes. For instance, there might be a design requirement where the map widget is implemented on large and medium screen sizes, but not on small screen sizes. In this case, you would just simply remove the map widget from the small screen size design and add it to the pending list.
Now that you a good understanding of the UI in Experience Builder, let's dive deeper and create an app.