ingestia.bi is 100% web — there is no native app in the App Store/Play Store. Instead, it's a PWA (Progressive Web App): you install it on your home screen from the browser itself, can receive push notifications and open deep links to a specific dashboard. This page explains what exists and why the cache on your device is deliberately "dumb" (it never stores data).
For the layout on small screens (a dedicated phone and tablet layout, or stacking when the owner hasn't arranged one), see Layout per device and TV mode; for reading the dashboard with your finger (tooltip that opens on tap, filters, cross-filtering), see Read a dashboard. This page covers the PWA/push layer.
What it is#
A PWA is a website the browser treats as an app: an icon on the home screen, opening in full screen (no address bar), notifications and a service worker (a local proxy that decides what to serve from the network and what to keep).
What it's for#
- Quick access: the dashboard becomes an icon on the leadership team's phones.
- Instant alerts: a KPI alert can arrive as a push notification.
- Direct link: share a deep link that opens exactly the right dashboard.
When to use it / when not to#
- Use it for executive consumption on the phone and occasional alerts.
- Don't count on offline use of the numbers: for security, the dashboard isn't available offline (see below). Offline you see a generic screen, with no data.
Install as an app#
Open ingestia.bi in your phone's browser
Use Safari (iOS ≥ 16.4) or Chrome (Android).
Add it to the home screen
On iOS: Share menu → "Add to Home Screen". On Android: menu → "Install app".
Open it from the icon
The app opens in full screen, with the brand icon.
Push notifications#
A dashboard alert (e.g., "Today's revenue below target") can be delivered as a push notification on the installed device.
- It depends on VAPID keys configured in the environment. Without the public key, the app simply doesn't subscribe to push — it degrades silently and never pretends it subscribed.
- You need to grant notification permission to the app.
- The traditional alert channels (email, WhatsApp, webhook) keep working in parallel — see Export and distribution and Alerts and webhooks.
Deep links#
A deep link opens the app directly on the right dashboard (and, when applicable, the right slice), instead of landing on the home page. Useful for pasting into an alert or a notification that takes you straight to the number.
Why the app never stores your data (secure cache)#
A service worker persists responses on the device — and that cache survives closing the tab, switching users and even signing out. If it stored the HTML/JSON of a dashboard, your workspace's financial data would leak. That's why the rule is strict:
| Content type | What the app does |
|---|---|
| Public static shell (icons, versioned assets, manifest) | Caches it (cache-first). |
Route HTML and data calls (/api/**, dashboard data) | Never caches it. Tries the network; offline shows a generic screen with no data. |
In other words: the installable app speeds up the shell (icons/styles), but all dashboard data always comes from the network, with your session and your RLS — nothing sensitive stays on the device.
Prerequisites#
- A compatible device (iOS ≥ 16.4 for push; current Android).
- For push: VAPID keys configured in the environment and the user's permission.
- An active session and a workspace with the published dashboard.
Limits and caveats#
- No native app and no offline use of the data (by security design).
- Installation behavior varies by browser/OS (iOS restricts push to apps added to the home screen).
Common mistakes#
- "I don't get push notifications": make sure you installed the app (iOS only delivers push to a PWA on the home screen), granted permission, and that the environment has VAPID configured.
- "Everything disappeared offline": expected — the app doesn't store data; reconnect to the network.
Related#
Last reviewed: 2026-09-08.