A full transition to components

Esri is fully committed to quality -based construction Web ingredients Which increases its core API Archigus Maps for JavaScript SDK In reusable customs HTML elements, such as . This applies to the internal development of the arix products as well as Bullet ui components already Which are presented as part of the Javascript Maps SDK. In fact, all basic widget functionality is already available as components. Today, the recommended approach to building web apps using SDK is to use components.

The benefits of ingredients

This change in architecture maximizes the production capacity of Front and Web Development. Customs elements provide an acquaintance (HTML, CSS, JS) programming experience and enable smooth integration with the application framework. Internally, the components are built using Of the calcite design system Ingredients, so they can be styled using alasite Design token (Via CSS). In addition, since we are surrounded by archess experiences as web components in ESRI products, we are able to provide proven workflows as the components of SDK in SDK (such as pre -released arcade editor and charts components). The combination of high levels of SDK will continue to grow over time.

From widgets to map ingredients

When the SDK was first formed, the standards of the web component were still strong, and the browser was not expanded. At the same time, we did not commit any specific JS framework because JS is a constant target of landscape. That is why we developed the widget architecture and over time, we made more than 60 wedge to use developers in our web apps. Now that the standards of the web component have been provided with all major browsers, we are able to develop our technology along with the browser (as we do for many SDK internal).

Initially, the widget is wrapped as web components, and over time, the component’s internals are being compensated with a better structure, which includes the elimination of a legacy widget architecture. To see a list of ingredients that complete this transition, see Release notes. Once we remove the components of components, we will add support for the slots, which will enable you to connect custom control and functionality in the component experience. Check Calcite Design System if you want to be aware of how the slot in the SD’s components will eventually work, as most of the calcites contains components Slot.

SDK’s website and its affiliated resources in the transfer

Many resources in the SD are already based on component. This includes new and latest resources such as gating start guides, programming pattern/excellent methods, lessons, a combination of samples, integration of component playground and API reference, and more. However, since the SDK’s website contains resources that we have been working on for 8 years, a complete transfer will cost numerous releases. When we are in the transfer, you will see samples and code pieces throughout the website that are not yet reflecting the recommended coding pattern (ie, not component). Every release will make remarkable progress.

Widget and Parts Road Map

Finally, all widgets will be removed and later. Therefore, developers are fully encouraged to transfer their UI code to use components in place of widgets and map view/scenewaves. The level of effort to migrate into a component UI will be very different among applications. In some cases, it will be very fast. In other cases, it may include a reasonable effort and requires planning and priority. Many ESRI product teams will go through the same migration. In this desired effort, the development road map of our components along with the Vegetable Road map factors. We are targeting the following milestone for a complete transfer to components:

• Once in a component @Arcags/Map Ingredients The package has been updated in their implementation so that the widget code can no longer wrap, the equivalent widget will be dismissed. Depression will be indicated in API reference, sample code, and console messages.
• All widgets will be outdated only in Q1 2026
• All widgets will be removed from SD in the early Q1 2027

Access to Basic Business Logic

While Presentation UI elements are being transferred from widgets to components, the basic business logic that is available (today via the view model). This means that you will be able to develop customs experiences and workflows by pushing SDK’s business logic. However, when we work to modernize and improve the SD, it is important for us to know how you are using business logic to inform your long -term roadmap. For example, some of the common stimulations here are why developers are using the view model that can be easily resolved by ESRI, which can include an option to the SDK component.

• UI simplicity, such as removing buttons/options: Configure option can be included in the ingredient that indicates whether a particular element is visible.
• Customs workflow integration: Slots can be added that enable you to embed a component of your choice within the UI. For example, a button can be integrated that launches the custom workflower. Additional events can also be included that allow you to react to user conversations or other terms.

Sometimes, view models are fully used to enforce custom workflows. A common example is the Sky View model used to handle interactive drawings on the map, which is essential for one aspect of the workflow. In this case, the advance sample will continue to rely on the SDK business logic for customs workflow.

If you are using a view model today, please fill out This survey So that we can use your input to notify SDK’s roadmap. We want to continue to offer an SD that provides maximum productivity when building your apps, and at the same time offers you the flexibility to enhance your organization’s specific needs.

Learn more about making apps with ingredients

There are many resources to learn how to make apps with ingredients. For example:

Start
Lead
Review of Components
Programming samples

2025 ESRI developer & Technology Summit: Special component session

This year, we will offer a presentation series of three parts covering the basic aspects of construction of web applications using Javascript Maps SD components. They are being presented by development teams that are working on the technology of components, and are recommended because they aim to provide basic information for developers who are either creating new apps or transferring apps to use components.