Metabase on Your Phone: How to Check Dashboards and Get Alerted on Mobile

June 2026 · 8 min read · Business

You built the dashboard. The numbers that tell you how the business is doing are sitting right there in Metabase — revenue, signups, churn, pipeline. And yet, somewhere between the laptop closing and the day starting, the dashboard goes unchecked. Not because you don't care, but because checking it means opening a laptop, finding the right tab, logging in again, and squinting at a chart that was never designed for a 6-inch screen.

This is the quiet failure mode of business intelligence: the dashboard nobody opens. The data is fine. The access is fine. What's missing is the last mile — getting the number in front of the person who needs it, at the moment it matters, on the device that's already in their hand.

Why there's no official Metabase mobile app

Metabase is one of the best things to happen to self-serve analytics. It's open-source, it's quick to stand up, and it lets people who don't write SQL answer their own questions. But it was built web-first, for the desktop, and that's where it shines. There is no official native iPhone or Android app.

What you get on a phone is the responsive web version, and it carries the friction of the web with it: you log in again (often with two-factor), you wait for a full dashboard to render, and then you pinch and pan around charts sized for a monitor. None of that is Metabase doing something wrong — it's simply that a browser tab can't do the three things a phone is uniquely good at.

The three things a phone can do that a desktop dashboard can't

When people say they want "Metabase on mobile," they rarely mean "the same dashboard, smaller." They mean three specific jobs that a desktop BI tool structurally cannot do:

Reach you. A dashboard waits to be opened. A phone can tap you on the shoulder. The single most valuable thing mobile adds to BI is a push notification when a number crosses a line you care about — even when no app is open.
Be glanceable. The best metric is one you don't have to go looking for. A Home- or Lock-Screen widget that shows today's revenue or active users turns "let me check" into "I already saw it."
Open instantly. Face ID, then your numbers. No login screen, no 2FA round-trip, no choosing a workspace. The whole interaction should be shorter than the thought that prompted it.

Your options for Metabase on mobile

There are a few honest ways to bridge the gap today, each with trade-offs:

Approach	Good for	The catch
Mobile web (Metabase in a browser)	Occasional deep dives; full feature set	Re-login + 2FA, slow render, charts sized for desktop, no push, no widgets
Email / Slack subscriptions	Scheduled digests at a fixed time	Push on a schedule, not on a change; static images you can't tap; clutters the inbox
Screenshots in a group chat	Sharing a single number with the team	Manual, instantly stale, no history, no alerting
Build your own (API + a script or app)	Teams with engineering time to spare	You're now maintaining an app; auth, caching, widgets and notifications are real work
A read-only mobile companion	Glancing, monitoring, and alerts on the go	It's read-only by design — you still author dashboards in Metabase itself

Metabase's own email and Slack subscriptions are genuinely useful and worth turning on. But a subscription fires on a schedule — 8am every weekday — not at the moment a metric actually moves. The gap that's left is real-time, glanceable, and personal.

What "good" looks like on a phone

If you're evaluating any mobile approach for Metabase, four things separate a toy from a tool:

Real, native charts — not a screenshot. You should be able to tap and scrub a line for the exact value at any point, and drop to the underlying table when you want the raw rows.
Alerts that fire on change — set a threshold on a metric and get a push the moment it crosses, ideally with some awareness of seasonality so a normal Monday spike doesn't wake you at 3am.
A plain-language read — a sentence that says what moved, by how much, and which related number moved with it. Most of the time you don't want to study the chart; you want the takeaway.
Privacy you can reason about — your dashboards are some of the most sensitive data your company has. A mobile layer should connect to your instance directly, not route your numbers through a third party's servers.

This is the gap we built Dashpocket to close. It's a private, read-only companion for Metabase: point it at your own instance and your dashboards become fast, native, tappable charts. Set a threshold on any metric and it pushes you the moment it crosses — even with the app closed. Pin your key numbers to Home- and Lock-Screen widgets, get a plain-language briefing generated on the device, and unlock with Face ID. It talks straight to your Metabase over HTTPS — there's no Dashpocket account and no Dashpocket server, and your credentials live only in your device's Keychain. Free to download (there's a sample-data demo, no account needed), with a one-time unlock — no subscription.

A 10-minute mobile monitoring setup

Whether you use Dashpocket or assemble your own stack, the principle is the same: stop checking, start being told. A setup that actually gets used looks like this:

Pick three to five numbers that matter. Not thirty. The metrics where a real move would change your day — revenue, signups, churn, error rate, cash.
Pin them where you'll see them. A widget on the Home or Lock Screen turns a deliberate check into a passive glance.
Set thresholds, not schedules. Decide what "abnormal" means for each metric and let an alert fire only when it happens. One good alert beats ten daily emails.
Keep one daily digest. A single morning scorecard for context is plenty — alerts handle the exceptions, the digest handles the trend.
Connect the "why." When a number moves, the next question is always why. Following the public news around your industry and competitors next to the metric is often half the answer.

Don't trade your numbers for convenience

It's worth saying plainly, because it's easy to overlook in the rush to get a dashboard on a phone: many mobile BI tools work by sitting between you and your data. Your queries and results pass through — and are sometimes cached on — a vendor's servers. For a marketing dashboard that might be fine. For revenue, headcount, or anything under NDA, it's a quiet expansion of who can see your most sensitive numbers.

The safer pattern is the boring one: a mobile layer that connects directly to the instance you already trust, stores credentials in the device's secure storage, and does any summarising on the device itself rather than shipping your numbers off to be processed. Convenience and confidentiality aren't actually in tension — you just have to insist on both.

The bottom line

Metabase is excellent at letting people ask questions of their data. The thing it can't do on its own is follow you out of the building. The fix isn't a smaller dashboard — it's a different shape entirely: a few numbers that find you, alerts that fire when something genuinely changes, and a glance that's faster than opening a laptop. Get that last mile right and the dashboard you built finally does the job you built it for.