Opening an app
Select Live Apps in the workspace console’s sidebar, then click an installed app’s name or its Open button. It opens inside the console. Copy the browser’s address to share that viewer with your team. To use the app on its own, select ⋯ → Open in new tab: the app fills the new tab, with no console menu, breadcrumbs or tabs around it, and that tab’s address is a link you can share. Wait for installation to finish and Open to become available. In a current browser, a static app always opens inside the console. Its own address works as a link you can share: whoever follows it lands on the app in their workspace, at the path and query the link pointed to. A slash at the very end of the link is dropped, as it is for any app opened inside the console, and a path whose segments contain anything other than letters, digits,-,
_, . and ~ opens the app at its first page. /reports/2024-q1 is kept; /reports/q1 final
is not. Whoever follows the link sees the app filling the tab, as Open in new tab shows it. An
app that runs its own server also opens on its own at its own address.
You’re already signed in, so opening an app never asks you to sign in again. The app sees your identity
on every request and queries the engine as you, so what you see reflects your own access, same as it
would if you ran the query yourself.
An app built from the dip app new --runtime frontend scaffold says so at the top of the page:
What does an app address look like?
A readable app address combines its app slug and your tenant slug, for examplehttps://revenue-dashboard--altimate.apps.adp.example.com. A slug is the short name used in an
address. Your deployment must enable readable app addresses on the app’s data plane.
Copy the address shown by the app. Long or already-reserved names can receive a stable suffix.
Renaming the app or your tenant’s display name keeps the assigned address. An existing link using
an installation ID continues to reach the same installation after its readable address is ready.
Existing installations receive a readable address on their next successful installation retry or
version change after the data plane enables this feature. Publishing a version alone does not move
an existing installation. Other data planes keep their installation-ID
addresses. A failed retry keeps the previously published address, but the installation reports
Install failed even if the existing app still serves that address. The owner or an app
administrator can inspect the reason and retry from the app’s detail page.
Waking up
An idle app scales down to save resources, and wakes again automatically the moment someone opens it. The first request after a while away shows a short “waking up” message that refreshes itself into the running app once it’s ready. This usually takes under a minute, and you don’t need to do anything but wait for it. If the app has been parked, opening it shows a message that it was parked and won’t wake on its own. Its owner with Manage own apps, or an app administrator, can wake it from its detail page.While you’re using it
- Real-time surfaces (Streamlit, WebSocket-based apps) stay warm as long as you’re actively connected. The idle clock only starts once you close the tab or disconnect.
- Sign-in never expires mid-session in a way that interrupts you. The platform refreshes your access behind the scenes.
- App pages load assets and make browser API requests only to their own Dippr app address. External APIs and CDN assets are blocked for every installed app. The page never receives an engine token; Dippr handles query credentials for it.
Picking a version
If the app’s author has published more than one version and the installation is pinned to a specific one, you see whatever version is installed. There’s no per-user version picker inside the viewer. Ask the app owner to change the installed version if you need a different one; see Changing version.Why does an app not open?
Apps built with the current SDK turn refused queries into an access message. It names a table only
when your current access already lets you list that table; otherwise it says this data. When an
owner’s display name is available, the message tells you whom to ask. It never substitutes their
email address. If the name is unavailable, it says the app’s owner.
The app cannot grant access or show you more data than you could query yourself. Signing in again
does not change a permission refusal.
Embedding
Inside the console, an app is shown in an isolated frame on its own address, so it’s a real security boundary rather than a same-page embed. Embedding a Dippr app in a page you host yourself, outside the console, isn’t supported today. The embedded app cannot open popups or submit browser forms. In a current browser, a static app is shown only this way. If a browser asks for a static app’s page as a tab of its own, Dippr sends it to the app in the console instead, where those limits apply. If the console’s address can’t be worked out, you see This app opens inside your workspace. Go to your workspace, select Live Apps, then open the app from there. If signing in to a static app keeps returning to the sign-in page, your browser is blocking the app’s cookies. The page names the app’s own address. In your browser’s settings, allow cookies for that address, then select Sign in. The app’s address can be on a different site from your workspace’s, so allowing cookies for the workspace alone may not be enough.Related
Install an app
What the consent screen means, and how an app owner changes it later.
Data apps overview
The whole data app lifecycle, from scaffolding to use, at a glance.