Most Tableau dashboards are designed for desktop screens and are unusable on mobile. Yet executives and field teams often need analytical access on mobile devices. Designing for mobile is not about shrinking a desktop dashboard — it is about rethinking what information is needed, in what form, and how it is navigated on a small touch screen.
Tableau's mobile app and browser-based mobile access make dashboards available on phones and tablets. But availability is not usability. A dashboard designed for a 24-inch monitor and a mouse presents information at a scale and with an interaction model that does not translate to a 6-inch touch screen. Executives reading dashboards on phones, field sales teams checking metrics between meetings, and operations managers monitoring KPIs away from their desks all need analytical access — and all encounter dashboards that require pinching and zooming to find what they need.
Designing for mobile is a design problem, not a technical problem. The technical capability exists; the question is how to use it.
How Tableau Handles Mobile Layouts
Tableau has a built-in device preview and layout capability that allows creating separate layout versions for desktop, tablet, and phone. Each layout version can have different content positions, different element sizes, and different content visibility — you can show a simplified phone view while maintaining a detailed desktop view in the same workbook.
**Device layouts workflow**: In Tableau Desktop, the bottom of the window has a device type selector (Desktop, Tablet, Phone). When you select Phone or Tablet, Tableau shows a preview of how the dashboard renders at that device viewport. The first time you select a device type for a workbook that only has a desktop layout, Tableau offers to create an automatic phone layout from the existing desktop layout.
The automatic phone layout rearranges tiles in a single-column stack. It is a starting point, not a finished product — the automatic layout typically requires significant rework to be genuinely usable.
**Responsive sizing**: Set dashboard width to "Automatic" rather than fixed pixels to allow the layout to adapt to available viewport width. Combined with device-specific layouts, this provides the appropriate behaviour at each viewport range.
Design Principles for Mobile Dashboards
**One metric per screen**: A desktop dashboard can display 6-12 metrics in a grid. A phone dashboard should display one primary metric, with secondary context immediately below. If the user needs to scroll to see the first important number, the design has failed.
**Touch-appropriate targets**: Interactive elements (filters, navigation buttons, click targets on marks) must be at least 44x44 pixels — the minimum comfortable touch target. Mark sizes in Tableau scatter plots or geographic maps may need to be increased for touch-accurate selection.
**Remove everything that requires hovering**: Desktop dashboards often use tooltips as the delivery mechanism for detailed data — hover over a bar to see the exact value. On touch devices, hover does not exist; a tap shows the tooltip once and immediately dismisses on next tap. Reconsider any design that relies on tooltips for primary information delivery on mobile. Show key values as labels on marks or in a separate text field.
**Simplify navigation**: Desktop dashboards with many sheets and navigation buttons work because a mouse makes precise clicking easy. Mobile navigation should use large, clearly labelled buttons with adequate spacing. Tab-based navigation between views is appropriate; complex button grids are not.
**Filter design for touch**: Small dropdown filters that work with a mouse pointer are difficult to operate with a finger. On mobile, use filter buttons (clickable chips or toggles) rather than compact dropdowns. Keep filter options to 5 or fewer for any filter visible on mobile; complex multi-select filters should be rethought or moved to a secondary filter screen.
What Content to Include on Mobile
The most important mobile design decision is content selection — which metrics belong on the mobile view and which do not.
**Executive mobile**: The executive checking numbers between meetings needs the 3-5 most critical performance indicators with clear trend context and target comparison. Revenue vs target, pipeline coverage, customer count change, key operational metric. No detailed tables, no drill-down complexity. The executive can go to the desktop for depth; on mobile they need a health check.
**Field team mobile**: A sales rep or field service technician needs context-specific information: their own performance vs quota, their open opportunities or tickets, their schedule's next priority. The mobile design is personalised and operational, not a general performance overview.
**Operations monitoring mobile**: An operations manager monitoring a 24/7 process needs alert-style information: is anything outside normal range? Traffic light status indicators with drill-down available are more appropriate than trend charts that require careful reading.
Practical Implementation in Tableau
Start with the mobile use case, not the desktop:
1. Define the primary question the mobile user is asking and the one or two metrics that answer it
2. Design a phone layout that puts those metrics at the top, large, with clear comparison context
3. Add supporting context below (trend sparkline, supporting metric, period selector)
4. Test on an actual phone, not just the Tableau Desktop device preview — the preview is useful but does not replicate touch interaction
Publish to Tableau Server or Cloud and test in the Tableau Mobile app. The mobile app provides better performance than browser-based access on phones because it caches content locally and is optimised for the native mobile experience.
**Custom views and favourites**: Encourage mobile users to save custom views that match their preferred filter settings. A sales rep who always wants to see their own pipeline can save a custom view with their name pre-selected as a filter, making the mobile experience one tap away from their relevant data.
Our Tableau consulting practice designs dashboard experiences for all device types — contact us to discuss mobile analytics design for your Tableau environment.
A former Microsoft data architect audits your data foundation, identifies your top priorities, and sends you a written plan. Free. No pitch.
Book a Call →