A dashboard that is intended to be viewed on a mobile device should not be designed the same as one being viewed on a desktop. When you create a dashboard, you can create a separate mobile view of it that is optimized for viewing on mobile devices. It is recommended that a dashboard's mobile view complement the desktop view and that you keep the design simple. To design a dashboard's mobile view, start with a thorough understanding of the end user. When creating a mobile view, consider the following best practices.
Limit the number of elements
Since memory resources and screen space are less on mobile devices; it is recommended to limit the amount of data and visualizations. If a dashboard's mobile view has too many visuals, it is likely not focused enough and can affect performance for viewers. Keeping the number of elements to a minimum for a dashboard's mobile view can help keep information focused and ensure optimal functionality for the user.
Additionally, avoid using the embedded content element in your mobile view to embed other applications in your dashboard. When a dashboard with embedded content loads, the embedded content also loads, using more data and resources.
Optimize the view's layout
With limited space on a mobile screen, having all your elements in one page is not always optimal. As you configure the layout of your mobile view, group and stack your elements to create a layout that resembles multiple pages on the dashboard. Stacking creates a tabbed view of your elements, and on a mobile device, users can tap to switch tabs.
Minimize text
It is recommended that you minimize the amount of text on a dashboard's mobile view to communicate the information clearly. Some best practices for including text on your dashboard's mobile view include the following:
- Only add a header to your dashboard when it is necessary for reader comprehension. On a mobile view, a header can only include text and images.
- Limit the amount of text you place in each element's title and description (or omit text in these areas altogether).
- For all elements, keep the Last update text option off. Mobile views do not have refresh intervals, so knowing the last time the data was updated is not relevant for mobile users.
Configure for mobile screens
When using a mobile device, users are most likely using a touch screen to interact with the dashboard. This means that interactions should be minimal and easy to do on a touch screen. Some best practices for configuring your elements include the following:
- For the pie chart and serial chart, turn off the Hover text option.
- Disable pop-ups on a map's operational layers. Tapping a single feature on a mobile device is difficult, and there isn't as much space on the screen to show a pop-up on top of the map.
- Avoid using charts and maps with densely clustered data points as the source of actions because tapping a single data point can be difficult on smaller screens.
Create simple visualizations
Most mobile users have little or no need for in-depth visualizations as the small screen size of a mobile device is not suitable for in-depth analysis. Instead, dashboards that are viewed on mobile devices should be about conveying performance and values. Indicators and gauges are often the best visualizations, as information can be understood quickly and action can be taken immediately in response to it.
Build mobile-ready maps
Maps should be as simple as possible on your dashboard's mobile view. Some best practices for building mobile-ready maps include the following:
- A dashboard's mobile view should have a maximum of one map. This makes the load time of the dashboard faster and reduces the amount of data downloaded to the mobile device.
- Limit the map to one operational layer, with a minimum number of features, whose symbology contrasts with the background basemap. This makes the map easier to interpret and faster to draw and reduces the amount of data being downloaded to your device over a network connection.