ArcGIS development

Experience Builder custom widget development

When Experience Builder's standard widgets stop short of your workflow, we build the missing piece. Custom widgets are written in the Experience Builder developer edition with React and the ArcGIS Maps SDK for JavaScript, tested against your ArcGIS version, and handed over as code in your repository.

What a custom widget is for

Experience Builder covers most map apps through configuration. A custom widget fills the gap when a workflow needs logic, an integration or an interface that the standard widgets do not offer. We configure first and write code only where configuration stops, which keeps your apps easier to upgrade.

Widgets we build

NeedExample widget
Reports and printingA property or asset report that gathers attributes, related records and a map extract into a branded PDF
Guided editingA step-by-step form that validates edits against your business rules before they are saved
IntegrationsA panel that reads or writes records in a CRM, ERP, asset management or permitting system through its API
AnalysisBuffer, overlay or network queries with results shown as a table, chart and map selection
SearchSearch across several layers and external sources, with results ranked the way your users expect
Rebuilt Web AppBuilder widgetsA custom Web AppBuilder widget rewritten for Experience Builder, keeping the behaviour your users rely on

How a widget project runs

  1. Workflow first. We sit with the people who will use the widget and write down what they need to do, step by step.
  2. Prototype. A working first version in the developer edition, connected to a copy of your data, so the riskiest parts are tested early.
  3. Build. React components and the ArcGIS Maps SDK for JavaScript 4.x, with settings exposed so your GIS team can configure the widget without code.
  4. Test against your version. We test with the Experience Builder and ArcGIS Enterprise or ArcGIS Online versions you run.
  5. Deploy and hand over. The widget is deployed to your ArcGIS Enterprise or your own web server, depending on your setup, with build and deployment notes.

What you receive

  • Source code in a repository you own, with a readme for building and deploying it
  • A settings panel so the widget can be configured inside Experience Builder
  • Notes on the Experience Builder and ArcGIS versions it was tested against
  • A walkthrough with your GIS team

Frequently asked questions

Can you convert our Web AppBuilder widgets to Experience Builder?

They cannot be converted directly, because Web AppBuilder uses the ArcGIS API for JavaScript 3.x and Experience Builder uses version 4.x. We rewrite them, keeping the behaviour and improving it where the new platform allows. See our Web AppBuilder migration service.

Will a custom widget survive Esri upgrades?

Widgets built on the supported APIs are the most upgrade-safe option, but each Experience Builder release can change details. We note the versions a widget was tested on, and a maintenance arrangement can cover re-testing when you upgrade.

Can custom widgets be used with ArcGIS Online?

Yes, depending on how your organisation hosts Experience Builder apps. We confirm the right deployment route for your setup before the build starts.

Who owns the widget code?

Ownership is set in the contract. Our usual approach is to work in a repository you own from the first day.

Are you an Esri partner?

No. Jugrafiya is not an Esri partner. We build with ArcGIS products on client projects, and you license ArcGIS directly from Esri or your local distributor.

Need a widget Experience Builder does not have?

Tell us what your users need to do and which ArcGIS version you run. We will reply with questions and a suggested approach.

How we work: engagement models, ownership and handover