Install as an app

Add Teleprompt to the home screen or dock on iOS, Android, macOS and Windows.

Why install it

Teleprompt is a progressive web app, so installing it is not a download; it is the same site, given its own icon, its own window and no browser chrome. That matters more than it sounds:

The display gets the full screen, with no URL bar collapsing halfway through a take.
The remote launches straight into your scripts instead of a browser tab you have to find.
The app shell is kept on the device, so a slow venue network cannot leave you looking at a browser error two minutes before you go on.
There is a home-screen shortcut that opens the remote directly.

Install from this page

iPhone and iPad

Safari does not offer an install API, so this one is manual, and it has to be Safari; Chrome on iOS cannot add to the home screen.

Open Teleprompt in Safari.
Tap the Share button in the toolbar.
Scroll down and choose Add to Home Screen.
Confirm, then launch Teleprompt from the home screen rather than from Safari.

iOS note

Launched from the home screen, the app gets its own storage and its own sign-in session. You will be asked to sign in once more the first time, and then not again.

Android

Chrome, Edge and Samsung Internet all support installing directly. Use the button above, or open the browser menu and choose Install app / Add to Home screen.

macOS and Windows

In Chrome or Edge, look for the install icon at the right-hand end of the address bar, or open the menu and choose Install Teleprompt. In Safari on macOS, use File → Add to Dock.

A desktop install is genuinely useful for the display role: it opens in a window with no tabs, which is one fewer thing that can appear on a shared screen.

What works offline

The service worker keeps the app shell, the icons and pages you have already visited. Navigations are network-first with a short timeout, so you always get the live page when the network is reachable and a real offline page when it is not.

API responses are never cached. A stale script or a stale room state would be worse than an error, so those always go to the server.

A live room needs a connection in any case: the two devices have to find each other before they can talk directly. See Troubleshooting if a session will not connect.