SiteGlance — native iOS and Android client for Umami, with home screen widgets

[xcc3641]

I self-host Umami for a few personal sites. Checking one number meant opening the dashboard in a mobile browser, so I built a native client.

SiteGlance is an unofficial iOS and Android app. It reads your Umami instance. It does not replace the tracker, and it is not affiliated with the Umami project.

How it connects

• Self-hosted: the app signs in to your instance and calls its API directly. No relay server.
• Umami Cloud: sign in via API key.
• Credentials stay in the iOS Keychain or Android Keystore. There is no external analytics SDK.
• Aimed at current Umami v2 (v1 is not supported).
• Goals need v2.12+; Funnels need v2.3+.
• The instance has to be reachable over HTTPS from the phone. A reverse proxy is fine (Nginx, Traefik, Caddy, Cloudflare Access) as long as /api is actually Umami\x27s API and not an HTML login wall or a stripped path.

What you can do without opening the dashboard

• Today\x27s visitors and hourly trends on a home screen widget (one widget per site, widgets are free).
• Widgets are updated by system background fetch (iOS ~15 min, Android ~30 min). Opening the app pushes a fresh snapshot immediately.
• In the app: active visitors, top pages, referrers, devices, countries, plus goals and funnels where your Umami version supports them.

Free and Pro

• Free: 1 connection you add yourself, your first 3 sites, widgets, and the top rows of metric breakdowns.
• Pro (one-time unlock): unlimited connections/sites, and full breakdowns including goals and funnels.

Links

• iOS: https://apps.apple.com/app/id6813091770
• Android: https://play.google.com/store/apps/details?id=com.hugo.siteglance
• Website & Web Demo: https://siteglance.yichenlab.com/

If you try it against a proxy setup and it fails, a description of the proxy (and whether /api/websites works in a browser while logged in) is much more helpful than a screenshot of the error toast. Happy to patch edge cases!