Why a portfolio of 19 client-first custom widgets is a faster, lower-risk path to modern ExB capabilities than custom development or new server infrastructure.
ArcGIS Experience Builder is the default web-GIS builder for Esri customers, but each time a team needs a capability that sits outside its box, the same pattern repeats:
The cumulative cost is felt as slow time-to-capability: weeks-to-months of engineering for capabilities that are now table-stakes in the broader data ecosystem.
Adopt a curated portfolio of 19 ExB custom widgets (17 available today, 2 on the roadmap) from TMG, organized into six capability areas. Two architectural decisions define the value:
The portfolio is not a single product: teams adopt only the widgets that map to their use cases, and because all widgets share a common foundation and follow the standard ExB pattern, they compose cleanly inside one experience.
Several converging trends make the timing strong for this kind of portfolio:
Teams that standardize on a coherent widget portfolio now avoid accumulating bespoke integrations later.
| Benefit area | What you get |
|---|---|
| Speed | Weeks-to-months of custom development replaced with drop-in adoption; capabilities live in days. |
| Cost avoidance | No new servers to host, secure, patch, or monitor for most widgets; reduced middleware sprawl. |
| Security & compliance | Sensitive data stays in the browser — supports GDPR/HIPAA/SOC 2, air-gapped, and sovereign-data postures. |
| Portability | Open standards (OGC, STAC, IMDF, CoT, GTFS, Iceberg, Delta) keep you off proprietary rails. |
| Quality | Production-hardened flagship (input validation, SQL-injection prevention, error boundaries, tests) — not prototype-grade. |
| Esri alignment | Native integration with FeatureServers, SceneView, Calcite/Jimu UI, ArcGIS Maps SDK — extends your existing investment. |
Costs fall into three categories. Exact figures depend on licensing tier and deployment; treat the ranges below as planning estimates to confirm during procurement.
| Cost category | Description | Relative magnitude |
|---|---|---|
| Widget licensing / support | Per-widget or portfolio licensing, optional commercial support and SLAs. Widget source is Apache-2.0 / MIT. | Low–Medium (TBD with vendor) |
| Integration effort | Deploying widgets into ExB, configuring data sources, training app authors. Lighter than custom dev. | Low (days per widget) |
| Internal operations | For most widgets, near-zero ongoing ops (no server). A few widgets (e.g., BigQuery & Sheets) include an optional Node.js backend. | Very Low |
Return is best framed as cost-and-time avoidance plus risk reduction, rather than a single payback number:
| Path | Build effort | Server footprint | Time to live |
|---|---|---|---|
| Custom build | Weeks–months of specialist dev | New middleware service | Months |
| TMG widget adoption | Days of configuration | None (client-side) | Days–weeks |
Multiply across the 2–3 capabilities most relevant to your organization to estimate portfolio-level avoidance. These are directional comparisons, not a quoted ROI — confirm with your own build estimates during evaluation.
| Risk | Mitigation |
|---|---|
| Widget maturity varies across the portfolio | Adopt the production-hardened widgets first (e.g. DuckDB Advanced Analytics); treat roadmap items (3D Buildings, LLM Chatbot) as future, not current, capability. |
| Browser compute limits on very large datasets | Widgets stream/filter (bbox, view extent, range requests); validate against your largest realistic datasets in the pilot. |
| Dependency on third-party services (e.g. Street View/Bing, TiTiler) | Where relevant, widgets are configurable (custom TiTiler, custom STAC endpoints); Street View/Oblique uses public provider URLs and documents the constraint. |
| Vendor continuity / single source | Permissive Apache-2.0 / MIT licensing means the widget source is yours to maintain; commercial support is additive, not a dependency. |
| Internal change management | Widgets follow the standard ExB pattern — minimal new tooling for existing ExB app authors. |
| Alternative | Trade-off |
|---|---|
| Custom in-house development per capability | Maximum control, but highest cost, slowest time-to-capability, and full ops burden. Justified only for differentiating workflows. |
| Single-vendor proprietary platform swap | Avoids some integration work but abandons the Esri investment and introduces lock-in — contrary to most organizations' strategy. |
| Do nothing / defer | No cost, but capability gap and integration debt continue to grow; competitors and peer agencies modernize faster. |
| Adopt TMG portfolio (recommended) | Lowest combined cost, fastest time-to-capability, preserves Esri investment, open standards avoid lock-in. |
Adopt the TMG widget portfolio for non-differentiating modern capabilities, and reserve in-house engineering for the workflows that are genuinely differentiating for your organization. Concretely: