{
  "id": "arcgis-experience-builder-vs-arcgis-dashboards",
  "ids": [
    "arcgis-experience-builder",
    "arcgis-dashboards"
  ],
  "title": "ArcGIS Experience Builder vs ArcGIS Dashboards: publishing ArcGIS maps for different audiences",
  "heading": "ArcGIS Experience Builder vs ArcGIS Dashboards",
  "kicker": "GIS and analysis software comparison",
  "deck": "Experience Builder is for composing a web application around maps and widgets. Dashboards is for presenting operational indicators and linked data views. Choose according to whether the audience needs a broader application journey or a monitoring screen.",
  "description": "Compare ArcGIS Experience Builder vs ArcGIS Dashboards for publishing ArcGIS maps for different audiences.",
  "answerHeading": "Which option fits the requirement?",
  "answer": "Experience Builder is for composing a web application around maps and widgets. Dashboards is for presenting operational indicators and linked data views. Choose according to whether the audience needs a broader application journey or a monitoring screen.",
  "checkedAt": "2026-10-25",
  "researchTag": "Deployment, compatibility and cost scope",
  "researchLimit": "Official product material reviewed. Acceptance checks are proposed exercises, not completed product trials, performance measurements or reliability guarantees.",
  "datasetDescription": "Seven technical differences and four proposed acceptance checks for ArcGIS Experience Builder vs ArcGIS Dashboards.",
  "type": "workflow-buying",
  "sharedBuyingNeed": "Evaluate alternative approaches to publishing ArcGIS maps for different audiences.",
  "rows": [
    [
      "Output model",
      "Configurable web application",
      "Operational information dashboard"
    ],
    [
      "Authoring approach",
      "Visual layouts and widgets",
      "Configure maps, indicators and dashboard elements"
    ],
    [
      "Data context",
      "Connected ArcGIS maps and data",
      "Maps and connected data views"
    ],
    [
      "Interaction focus",
      "Custom layouts and multi-widget experiences",
      "Monitoring indicators and interacting with data"
    ],
    [
      "Platform boundary",
      "Eligible ArcGIS platform and user access",
      "ArcGIS organisation and sharing permissions"
    ],
    [
      "Evaluation focus",
      "Responsive layouts, widgets and data interactions",
      "Indicator definitions, filters and update behaviour"
    ],
    [
      "Cost components",
      "Eligible access, data hosting, services and custom work",
      "Eligible access, underlying services and hosted data"
    ]
  ],
  "scenarios": [
    {
      "name": "Audience task",
      "question": "Can the team build one copied view that answers a specific visitor question?",
      "left": "With ArcGIS Experience Builder, build one copied view that answers a specific visitor question.",
      "right": "With ArcGIS Dashboards, build one copied view that answers a specific visitor question.",
      "note": "The intended audience can complete the task using the available interaction."
    },
    {
      "name": "Mobile layout",
      "question": "Can the team read the app and operate its essential controls on a narrow screen?",
      "left": "With ArcGIS Experience Builder, read the app and operate its essential controls on a narrow screen.",
      "right": "With ArcGIS Dashboards, read the app and operate its essential controls on a narrow screen.",
      "note": "Content, controls and data remain understandable and usable."
    },
    {
      "name": "Sharing permissions",
      "question": "Can the team open the published test content as an anonymous and an authorised user?",
      "left": "With ArcGIS Experience Builder, open the published test content as an anonymous and an authorised user.",
      "right": "With ArcGIS Dashboards, open the published test content as an anonymous and an authorised user.",
      "note": "Apps and underlying layers follow the documented access policy."
    },
    {
      "name": "Content update",
      "question": "Can the team change one authorised sample record and inspect the published view?",
      "left": "With ArcGIS Experience Builder, change one authorised sample record and inspect the published view.",
      "right": "With ArcGIS Dashboards, change one authorised sample record and inspect the published view.",
      "note": "The update and ownership process is documented and repeatable."
    }
  ],
  "exampleTable": {
    "caption": "Proposed checks using authorised copies of representative datasets, projects or models. Record software versions, required licences, dependencies, configuration and observed results.",
    "headers": [
      "Requirement",
      "Proposed exercise",
      "Accept when"
    ],
    "rows": [
      [
        "Audience task",
        "Build one copied view that answers a specific visitor question.",
        "The intended audience can complete the task using the available interaction."
      ],
      [
        "Mobile layout",
        "Read the app and operate its essential controls on a narrow screen.",
        "Content, controls and data remain understandable and usable."
      ],
      [
        "Sharing permissions",
        "Open the published test content as an anonymous and an authorised user.",
        "Apps and underlying layers follow the documented access policy."
      ],
      [
        "Content update",
        "Change one authorised sample record and inspect the published view.",
        "The update and ownership process is documented and repeatable."
      ]
    ]
  },
  "sections": [
    {
      "id": "scope-and-architecture",
      "navLabel": "Architecture",
      "title": "Scope and architecture",
      "paragraphs": [
        "Experience Builder is for composing a web application around maps and widgets. Dashboards is for presenting operational indicators and linked data views. Choose according to whether the audience needs a broader application journey or a monitoring screen.",
        "These applications present geographic information in different ways and can be combined. An operational dashboard, interactive web application and narrative story have different audience tasks. Confirm user types, public access, underlying layer permissions and any separately billed services."
      ],
      "links": [
        {
          "url": "https://www.esri.com/en-us/arcgis/products/arcgis-experience-builder/overview",
          "label": "ArcGIS Experience Builder product information"
        },
        {
          "url": "https://www.esri.com/en-us/arcgis/products/arcgis-dashboards/overview",
          "label": "ArcGIS Dashboards product information"
        }
      ]
    },
    {
      "id": "cost-and-migration",
      "navLabel": "Costs & migration",
      "title": "Cost and migration planning",
      "paragraphs": [
        "For ArcGIS Experience Builder, include eligible access, data hosting, services and custom work. For ArcGIS Dashboards, include eligible access, underlying services and hosted data. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration.",
        "Publish a copied map with test data, verify it as an anonymous visitor and an authorised user, and check its layout on a small screen. Preserve required layer access and document who owns the app, data and updates."
      ]
    }
  ],
  "faqs": [
    {
      "question": "How should we choose between ArcGIS Experience Builder and ArcGIS Dashboards?",
      "answer": "Experience Builder is for composing a web application around maps and widgets. Dashboards is for presenting operational indicators and linked data views. Choose according to whether the audience needs a broader application journey or a monitoring screen."
    },
    {
      "question": "Which costs belong in the comparison?",
      "answer": "For ArcGIS Experience Builder, include eligible access, data hosting, services and custom work. For ArcGIS Dashboards, include eligible access, underlying services and hosted data. Define the same task, inputs, required outputs and operating environment, then confirm current terms for the actual software configuration."
    },
    {
      "question": "What should we validate before a production move?",
      "answer": "Publish a copied map with test data, verify it as an anonymous visitor and an authorised user, and check its layout on a small screen. Preserve required layer access and document who owns the app, data and updates."
    }
  ],
  "sources": [
    {
      "url": "https://www.esri.com/en-us/arcgis/products/arcgis-experience-builder/overview",
      "facts": "Official product scope, deployment and integration context used for publishing ArcGIS maps for different audiences."
    },
    {
      "url": "https://www.esri.com/en-us/arcgis/products/arcgis-dashboards/overview",
      "facts": "Official product scope, deployment and integration context used for publishing ArcGIS maps for different audiences."
    }
  ],
  "relatedLinks": [
    {
      "path": "/categories/gis-geospatial/",
      "title": "Gis Geospatial software"
    },
    {
      "path": "/guides/software-buying-checklist/",
      "title": "Software buying checklist"
    }
  ]
}