Use the dashboard's direct URL with view-only or kiosk options (Grafana: ?kiosk and a refresh interval such as &refresh=1m), sign in once inside the app so the session persists, and design a phone-sized dashboard rather than shrinking the desktop one. Keep the URL https and behind authentication.
Build a phone dashboard
A 12-panel desktop dashboard is unreadable on a phone. Make a dedicated mobile dashboard: 4–6 single-stat or small time-series panels, stacked vertically, big numbers. In Grafana, panels stack automatically on narrow screens — order them by importance.
Kiosk and refresh
Add ?kiosk (or &kiosk) to hide Grafana's navigation, and &refresh=1m to auto-update. Don't refresh every few seconds on mobile data — it drains battery and data.
Authentication
Sign in once in the app; the session cookie persists. If your instance uses Google OAuth, it'll be blocked in the WebView — use another provider or Grafana's own login for the app. Avoid putting tokens or API keys in the start URL; anyone can read it from the APK (security checklist).
Alerts
Alerts are better as push or chat notifications than as a dashboard you keep open. Route Grafana alerts to your chat app; use the dashboard app for context when an alert lands.
FAQ
Can I make an app of my Grafana dashboard?
Yes. Use a kiosk URL and sign in inside the app.
Is it safe?
Keep the dashboard behind login and https, and never embed tokens in the start URL.