GIS guides

Experience Builder, Instant Apps or Dashboards: Choose the User’s Next Action

Choose an ArcGIS app builder by the action a person must complete, then test the simplest candidate against that task.

Resident uses a tablet beside a street map outside a public library.

Choose an ArcGIS app builder by the action a person must complete, then test the simplest candidate against that task.

Finish this sentence first

“After opening the app, the user should be able to…” is a better starting point than “we want a dashboard.” Find a nearby facility, inspect a status summary and complete a multi-step investigation are different jobs.

Instant Apps offers focused mapping templates. Dashboards presents interactive indicators and visualizations. Experience Builder supports configurable layouts and connected widgets. These are starting points for evaluation, not hard boundaries that make every choice automatic.

Three branches for one facilities dataset

User's actionFirst candidate to evaluateEvidence needed before choosing
Find a facility near a searched locationA suitable Instant Apps templateSearch, results and details work for the actual audience
Review service status across facilitiesDashboardsDefinitions and filters answer the supervisor's question
Move through linked map, detail and comparison viewsExperience BuilderRequired interactions work clearly on intended screen sizes

A hypothetical public library finder needs location search, opening information and a useful result on a phone. Start by testing a focused template. Do not commission a complex multi-page experience merely because the dataset also contains fields that could become charts.

The request changes

The internal team then asks to compare facility capacity, inspect supporting records and switch between linked views. Treat this as a second audience and task. It may justify another application or a more configurable experience; it does not automatically belong inside the public finder.

Write two acceptance scenarios. The public visitor must find a suitable facility without organizational knowledge. The internal reviewer must explain a comparison using the relevant records. If one interface makes either task substantially harder, separate the experiences while maintaining shared authoritative data where appropriate.

Evaluate the unglamorous details

Test anonymous access if the app is intended to be public, and signed-in access if it is not. Verify the Arabic labels, reading order, keyboard journey, empty results and behavior when a linked item is unavailable. Product accessibility features do not remove the need to test your configured content.

Record the selected candidate, unmet requirements and who maintains the data and application. A small working acceptance demonstration is a stronger basis for selection than a long comparison of features nobody needs. This guide is a design exercise, not a claim that the example apps have been implemented.

For related preparation, read defining dashboard measures. Discuss this workflow with InfoGraph or review relevant GIS training.