| Concept | Description |
|---|---|
| Foundations | |
| Why Mobile BI Matters | Dashboards are increasingly more likely to be opened on a phone in a corridor than on a laptop at a desk |
| Mobile BI Tools | |
| Power BI Mobile | iOS Android and Windows apps with phone layouts, offline access, and push alerts |
| Tableau Mobile | iOS and Android apps with device-specific layouts via Device Designer |
| Looker Mobile | iOS and Android apps with responsive dashboards and offline preview |
| Qlik Sense Mobile | iOS and Android apps with offline mode and Mobile SDK for embedded use |
| Vendor-Specific Apps | Domo, Sisense, ThoughtSpot, others with similar feature sets |
| Browser-Responsive Web Apps | Some BI tools rely solely on responsive web rather than native apps |
| Mobile Differs From Desktop | |
| Screen Width Difference | Phone 375 to 430, tablet 768 to 1280, desktop 1366 to 4K pixels |
| Screen Orientation | Phone is portrait dominant; desktop is landscape |
| Touch versus Mouse | Touch with fingers, pinch and swipe versus mouse and keyboard |
| Session Length | Phone seconds to a minute; desktop minutes to hours |
| Network on Mobile | Mobile data and intermittent network versus office Wi-Fi |
| Audience Attention | Distracted, in motion versus focused at desk |
| Responsive Design Principles | |
| Breakpoints | Define explicit phone, tablet, and desktop layouts; do not rely on automatic resize |
| Vertical Stacking | Phone layouts vertically stacked; user scrolls top-to-bottom |
| Most-Important-First | Top of phone screen carries the headline; everything else below |
| Touch Targets | Minimum 44 by 44 pixels for buttons and slicers; finger-sized |
| Reduced Complexity | Three to five tiles on a phone, not twenty |
| Larger Text | Phone-readable headline numbers 24+ pt; axis labels still legible |
| Single-Column Charts | Side-by-side desktop charts almost always need to stack vertically on phone |
| Offline Tolerance | Phone connections drop; design for offline rather than against it |
| Fast Initial Render | Phone users expect content within 2 seconds; multi-second loads kill engagement |
| Power BI Phone Layout | |
| Power BI Phone Layout | Per-report alternate layout designed in Power BI Desktop View Mobile Layout |
| Power BI Mobile View Dashboard | Built directly in the Power BI Service for pinned-tile dashboards |
| Tableau Device Designer | |
| Tableau Device Designer | Tableau Desktop feature for separate Desktop, Tablet, and Phone layouts |
| Phone Tablet Desktop Layouts | Same workbook URL serves all three devices; only rendering changes |
| Push Notifications and Alerts | |
| Power BI Data Alerts | Threshold-based notifications pushed when refresh produces a value crossing the threshold |
| Power BI Pulse | Daily digests with AI-driven narrative delivered to Power BI Mobile feed |
| Tableau Subscriptions and Alerts | Email-based alerts that Tableau Mobile surfaces alongside the report library |
| Power Automate Cross-App | Power Automate routes alerts to Teams, SMS, custom apps when alerts fire |
| Real-Time on Mobile | |
| DirectQuery and Direct Lake on Mobile | Power BI live connections that work the same on mobile as desktop |
| Live Connection on Mobile | Tableau live connections rendered the same on mobile as desktop |
| Streaming Dataset on Mobile | API-pushed events visible on Power BI Mobile streaming tiles |
| Battery Considerations | Constant polling drains battery; configure refresh rate to genuine need |
| Data Plan Considerations | Streaming over mobile data is costly; consider Wi-Fi-only policies |
| Visible Update Cues | Live-updating chart needs refresh icon and as-of timestamp so user knows freshness |
| Foreground versus Background | Mobile OS may suspend background polling; design with this rather than against it |
| Authentication and Security | |
| Single Sign-On | Power BI and Tableau Mobile use Entra ID or corporate identity provider |
| Multi-Factor Authentication | Strongly recommended for any mobile BI deployment |
| Conditional Access | Restrict mobile access from outside trusted networks or non-managed devices |
| Mobile Device Management | Microsoft Intune, VMware Workspace ONE to enforce device policies |
| App Protection Policies | Restrict copy-paste, screenshots, exports from BI apps on personal devices |
| Sensitivity Labels on Mobile | Microsoft Information Protection labels travel with mobile exports |
| Sign-Out and Idle Timeouts | Force re-authentication after defined inactivity |
| Best Practices | |
| Design Phone-First | For mobile-heavy audiences (field staff, frontline managers, executives in motion) |
| Use Native Phone Layout | Power BI Phone Layout, Tableau Device Designer; not auto-resize |
| Limit to 3 to 5 Visuals | Most consequential KPIs and one trend; not all desktop visuals belong on phone |
| Stack Vertically Big Text | Single column, headline numbers at the top, larger fonts |
| Test on Real Phone | Test on a real phone, not just the design preview |
| Set Up Alerts | Threshold-based notifications that arrive without opening the dashboard |
| Document Offline Expectations | Power BI mobile caches recent reports; document the offline expectation |
| Sensitivity and Conditional Access | Required for confidential data on personal devices |
| Same URL Across Devices | One link, three layouts; users should not need to know the difference |
| Common Pitfalls | |
| No Phone Layout Pitfall | Pitfall of audience opening desktop layout on phone; pinch-and-zoom hell |
| Tiny Text Pitfall | Pitfall of axis labels and titles unreadable at phone size |
| Too Many Tiles Pitfall | Pitfall of twenty desktop tiles auto-resized to phone with nothing readable |
| Click-Hover Interactions Pitfall | Pitfall of tooltip-on-hover interactions never accessible on touch |
| Slow Mobile Load | Pitfall of heavy report taking ten seconds on mobile data; user gives up |
| Ignoring Touch Targets | Pitfall of 16-pixel slicer button useless on touch |
| No Push Alerts | Pitfall of expecting audience to open the dashboard daily and notice anomalies |
| Mobile Without Security | Pitfall of confidential data accessible from any phone with the password |
| No Offline Tolerance | Pitfall of audience on a flight finding nothing works |
| Never Tested on Mobile | Pitfall of designer never opening the dashboard on a real phone |
47 Mobile BI and Responsive Design
47.1 Why Mobile BI Matters
A dashboard is increasingly more likely to be opened on a phone in a corridor than on a laptop at a desk.
A growing share of dashboard consumption happens on phones and tablets. A field-sales manager checks performance between store visits. A plant supervisor reads a quality scorecard during the shift change. A hospital administrator opens an occupancy view during ward rounds. A senior leader checks the previous day’s KPIs on the morning commute. The phone, not the laptop, is becoming the primary screen for many BI consumers.
Designing for the phone is not the same as designing for the laptop. Screen real estate is a fraction; touch replaces mouse; bandwidth varies; sessions are short. The principles that make a dashboard work on a 1366-pixel laptop fail on a 375-pixel phone unless the design adapts.
The original treatment of responsive layout is Responsive Web Design by Ethan Marcotte (2011), whose principles have spread from web design to BI. The dashboard-specific guide remains Information Dashboard Design by Stephen Few (2013), with its emphasis on what to keep when space is scarce.
For a visualisation-focused book, this final BI-architecture chapter closes the consumption arc: the same dashboard built in earlier chapters must reach its audience on whichever screen they are using.
47.2 The Mobile BI Landscape
TipMobile BI Tools
| Tool | Mobile Capability |
|---|---|
| Power BI Mobile | iOS, Android, and Windows apps; phone layouts; offline access; push alerts |
| Tableau Mobile | iOS and Android apps; device-specific layouts via Device Designer |
| Looker Mobile | iOS and Android apps; responsive dashboards; offline preview |
| Qlik Sense Mobile | iOS and Android apps; offline mode; Mobile SDK for embedded use |
| Domo, Sisense, ThoughtSpot | Vendor-specific mobile apps with similar feature sets |
| Browser-Responsive Web Apps | Some BI tools rely solely on responsive web for mobile rather than native apps |
The two most-used native apps in enterprise contexts are Power BI Mobile and Tableau Mobile. Both auto-render web reports, but properly designed device-specific layouts — Phone Layouts in Power BI, Phone Layouts in Tableau Device Designer — produce a substantially better experience.
47.3 Mobile Differs From Desktop
TipWhat Changes on Mobile
| Dimension | Desktop | Mobile |
|---|---|---|
| Screen width | 1366 to 4K | 375 to 430 px (phone), 768 to 1280 px (tablet) |
| Screen orientation | Landscape | Portrait dominant |
| Input method | Mouse and keyboard | Touch (fingers); pinch and swipe gestures |
| Session length | Minutes to hours | Seconds to a minute |
| Network | Office Wi-Fi | Mobile data; intermittent |
| Audience attention | Focused | Distracted, in motion |
| Rendering speed | Fast | Variable |
The implication: mobile dashboards must show fewer KPIs, larger numbers, simpler charts, larger touch targets, faster loads. A dashboard with twenty visuals on a desktop becomes three KPIs and one trend line on the phone — and that is the right answer.
47.4 Responsive Design Principles for BI
The principles of Ethan Marcotte (2011) — fluid grids, flexible images, media queries — translate to BI as a small set of practical rules:
- Breakpoints: Define explicit phone, tablet, and desktop layouts; do not rely on automatic resizing.
- Vertical Stacking: Phone layouts are vertically stacked; the user scrolls top-to-bottom rather than side-to-side.
- Most-Important-First: Top of the phone screen carries the headline; everything else is below.
- Touch Targets: Minimum 44 by 44 pixels for buttons and slicers; finger-sized.
- Reduced Complexity: Three to five tiles on a phone, not twenty.
- Larger Text: Phone-readable headline numbers (24+ pt); axis labels still need to be legible.
- Single-Column Charts: Side-by-side charts that worked on desktop almost always need to stack vertically on phone.
- Offline Tolerance: Phone connections drop; a dashboard that requires constant connectivity will fail at the wrong moment.
- Fast Initial Render: Phone users expect content within 2 seconds; multi-second loads kill engagement.
47.5 Power BI Phone Layout
Power BI’s Phone Layout is a per-report alternate layout the analyst designs explicitly. The Service automatically serves the phone layout when the user opens the report on the Power BI mobile app.
To configure a Phone Layout in Power BI Desktop:
- Open the report.
- View → Mobile Layout.
- A blank phone-shaped canvas appears with the report’s visuals listed in the right pane.
- Drag the visuals onto the canvas in the order and size you want.
- Use only the most important 3–5 visuals; not all desktop visuals need to appear on phone.
- Save and publish.
When the report is opened in the Power BI Mobile app, the phone layout takes over. The desktop layout is unchanged for browser and tablet users.
For dashboards (the pinned-tile collections in Power BI Service), there is a separate Mobile View built directly in the Service. Open the dashboard → Edit → Mobile Layout.
47.6 Tableau Device Designer
Tableau’s Device Designer lets the analyst design separate layouts for Desktop, Tablet, and Phone within the same workbook (covered briefly in Chapter 33).
In Tableau Desktop:
- On the Dashboard pane, click + Phone or + Tablet to add a new device layout.
- The phone layout starts as auto-generated; toggle to Custom for full control.
- Tableau lists every dashboard object in a tree; toggle visibility to choose which appear on phone.
- Resize and reorder; switch container orientation from horizontal to vertical for stacking.
- Larger text sizes and bigger touch targets are essential.
- Publish to Tableau Server / Cloud; Tableau Mobile auto-serves the device-appropriate layout.
The same workbook URL serves all three devices; only the rendering changes.
47.7 Push Notifications and Alerts
Mobile is uniquely suited to push notifications. The audience does not need to open a dashboard to receive a critical update.
Power BI Data Alerts: A user (or admin) configures a threshold on a tile (e.g., NPS drops below 40); when the data refresh produces a value crossing the threshold, the Mobile app pushes a notification.
Power BI Pulse: Daily digests of selected metrics with AI-driven narrative, delivered to the Power BI Mobile feed.
Tableau Subscriptions and Data-Driven Alerts: Email-based alerts that the Tableau Mobile app surfaces alongside the report library.
Power Automate: For cross-app workflows — when a Power BI alert fires, post to Teams, send an SMS via Twilio, push to a custom mobile app.
The alert pattern shifts the burden from user remembers to check the dashboard to system tells the user when something matters. For mobile audiences moving between meetings, this is a major usability win.
47.8 Real-Time on Mobile
Real-time pipelines (Chapter 46) deliver to mobile dashboards the same way they deliver to desktop: through DirectQuery, Direct Lake, or Streaming Datasets in Power BI; through live connections in Tableau.
Practical considerations specific to mobile:
- Battery: Constantly polling a live source drains battery; configure the refresh rate to the genuine need.
- Data plan: Streaming several refreshes per minute over mobile data can be costly; consider Wi-Fi-only refresh policies.
- Visible updates: A live-updating chart on phone needs visual cues (small refresh icon, “as of” timestamp) so the user knows freshness.
- Foreground vs background: Mobile OS may suspend background polling; design for this rather than against it.
For most mobile audiences, near-real-time with push alerts delivers the practical value of live data without the battery and bandwidth cost of constant streaming.
47.9 Authentication and Security on Mobile
Phones are lost, stolen, and shared more often than laptops; mobile BI security has its own concerns:
- Single Sign-On (SSO): Power BI and Tableau Mobile use Entra ID / Azure AD or the firm’s identity provider; users authenticate once with their corporate credentials.
- Multi-Factor Authentication (MFA): Strongly recommended for mobile.
- Conditional Access: Restrict mobile access from outside trusted networks or non-managed devices.
- Mobile Device Management (MDM): Microsoft Intune, VMware Workspace ONE, or similar to enforce device policies.
- App Protection Policies: Restrict copy-paste, screenshots, and exports from BI apps on personal devices.
- Sensitivity Labels: Microsoft Information Protection labels travel with exports; downloads on phone retain restrictions.
- Sign-Out and Idle Timeouts: Force re-authentication after defined inactivity.
A mobile BI deployment without these controls is a security incident waiting to happen.
47.10 Best Practices for Mobile BI
- Design phone-first for mobile-heavy audiences: Field staff, frontline managers, executives in motion.
- Use the tool’s native phone layout feature: Power BI Phone Layout, Tableau Device Designer; do not rely on auto-resize.
- Limit phone view to 3–5 key visuals: The most consequential KPIs and one trend.
- Stack vertically, big text: Single column, headline numbers at the top.
- Test on a real phone: Not just the design preview; the experience differs.
- Set up alerts: For threshold-based notifications that arrive without the user opening the dashboard.
- Document offline expectations: Power BI mobile caches recent reports; plan accordingly.
- Sensitivity labels and conditional access: Required for confidential data on personal devices.
- Keep the URL same across devices: One link, three layouts; users should not need to know about the difference.
47.11 Common Pitfalls
- No Phone Layout: Audience opens the desktop layout on a phone; pinch-and-zoom hell.
- Tiny Text: Axis labels and titles unreadable at phone size.
- Too Many Tiles: Twenty desktop tiles auto-resized to a phone; nothing readable.
- Click-Hover Interactions: Tooltips that require mouse hover; never accessible on touch.
- Slow Mobile Load: Heavy report rendering takes ten seconds on mobile data; user gives up.
- Ignoring Touch Targets: 16-pixel slicer button useless on touch.
- No Push Alerts: Audience expected to open the dashboard daily and notice anomalies; misses the events that matter.
- Mobile Without Security: Confidential data accessible from any phone with the corporate password; data-leakage risk.
- No Offline Tolerance: Audience opens the app on a flight; nothing works.
- Designed Once, Never Tested on Mobile: Designer never opens the dashboard on a real phone.
47.12 Illustrative Cases
A Field-Sales App for 1,200 Branch Managers
A retail bank publishes its branch-performance dashboard for 1,200 branch managers consumed predominantly on phones. The Power BI Phone Layout shows three KPIs (revenue, conversion, customer count) at the top, a single trend chart in the middle, and a one-line action prompt at the bottom. Push alerts notify managers if any KPI drops below threshold. Adoption rises from 15 % on the desktop layout to 80 % on the phone layout within three months.
A Hospital Operations Dashboard
A hospital administrator’s dashboard, designed for ward rounds, runs on iPad. The Tableau Device Designer tablet layout shows a real-time bed-occupancy heatmap, an admissions trend, and an exception queue. Touch-friendly slicers select wards. Push alerts notify of capacity-threshold breaches. The desktop version, used in the operations control room, is denser and complementary.
A Sales Leadership Pulse Digest
A retailer’s sales leadership receives a daily Power BI Pulse digest each morning at 7 AM IST. The digest shows three tracked metrics with natural-language narratives. Recipients click through to the live dashboard only when an anomaly is flagged — which is roughly twice a week, vs daily-emailed dashboards previously ignored.
47.13 Hands-On Exercise: Building a Power BI Phone Layout
Aim: Take a Power BI report from earlier chapters and build a Phone Layout that is genuinely usable on a 375-pixel-wide screen, complete with a data alert.
Deliverable: A .pbix file with both Desktop and Phone Layouts, plus a configured data alert that fires on a defined threshold.
47.13.1 Step 1 — Open the Existing Report
Use the Power BI report from Chapter 36 (the Yuvijen Stores DAX measure library) or any other published Power BI report.
In Power BI Desktop, open the file. The Desktop layout already shows multiple visuals — KPI cards, a region map, a category bar chart, a trend line, a customer table.
47.13.2 Step 2 — Switch to Mobile Layout View
- View → Mobile Layout.
- The canvas changes to a phone-shaped grey area.
- The right pane lists every visual on the desktop report.
- The phone canvas is empty; the analyst drags only the visuals to include.
47.13.3 Step 3 — Choose Three to Five Visuals for Phone
Drag onto the phone canvas, in vertical order:
- The Total Sales KPI card (large headline number at the top).
- The YoY Growth KPI card with traffic-light formatting.
- The Profit Margin KPI card.
- A Sales by Month line chart.
- A Top 5 Categories bar chart.
Skip the region map (too dense for phone), the customer table (too detailed), and the slicers (use mobile filters via tap rather than persistent slicers).
47.13.4 Step 4 — Resize and Position
- Make each KPI card span the full phone width (about 375 px).
- Stack them vertically with a small gap.
- Resize text in each KPI to a comfortable phone size (font size 24+ pt for headlines).
- Below the KPIs, place the line chart at full width, modest height (~250 px).
- Below that, the bar chart at full width.
- Use the alignment guides to keep visuals neatly stacked.
47.13.5 Step 5 — Save and Publish
- Switch back to View → Desktop Layout to verify it remains unchanged.
- File → Save, then Home → Publish to the Service.
- The Service stores both layouts under the same report.
47.13.6 Step 6 — Test on the Power BI Mobile App
- Install the Power BI Mobile app on your iOS or Android phone (free).
- Sign in with the same Power BI credentials.
- Navigate to the workspace and open the report.
- The phone layout takes over; verify it looks as designed.
- Tap visuals to drill, swipe to switch reports, pinch to zoom.
If anything is illegible or awkward, return to the Mobile Layout view in Desktop and refine.
47.13.7 Step 7 — Configure a Data Alert
- In the Power BI Service, navigate to a dashboard that pins one of the KPI tiles (create the dashboard if needed: open the report → pin the visual to a new dashboard).
- Click the bell icon on the pinned tile → Manage Alerts → + Add alert rule.
- Configure: When YoY Growth goes below 0%. Frequency: every refresh. Send notification.
- Save.
When the next refresh produces a year-over-year drop, the Power BI Mobile app pushes a notification with the value and a link to the report.
47.13.8 Step 8 — Connect Power Automate (Optional)
For richer notifications, route the alert through Power Automate to Teams or SMS:
- From the alert rule → Use Microsoft Power Automate to trigger additional actions.
- The flow editor opens.
- Add an action: Post a message in a chat or channel (Teams).
- Configure the channel and message text.
- Save.
Now an alert fires both on the phone (push notification) and to a Teams channel (visible to the wider team).
47.13.9 Step 9 — Connect to the Visualisation Layer
The hands-on closes the BI tools arc:
- Chapter 35 prepared data with Power Query.
- Chapter 36 built measures with DAX.
- Chapter 38 published to Power BI Service.
- Chapter 39 integrated with Microsoft 365.
- Chapter 44 explored ETL pipelines.
- Chapter 45 designed the warehouse beneath.
- Chapter 46 added real-time pipelines.
- This chapter delivers it all to the audience’s phone with appropriate adaptation.
The dashboard the audience experiences on their phone is the same data, the same model, the same measures — only the layout changes. Mobile is not a new dashboard; it is the same dashboard rendered for the screen the user actually holds.
TipFiles and Screen Recordings
Power BI file (yuvijen-mobile.pbix) showing both layouts, screenshots from the Mobile app, screenshot of the data alert configuration, and a short screen recording of the mobile experience and an alert firing will be embedded here.