The app, for Android.

One build for a phone and for a television. It finds a Palladium on your own network, or takes the five-character code the server shows.

Or take it from your own server, which is the shorter way: app and server are one release with one number, so a server hands out the app that matches itself. Open the server's address in a browser and press Install on a phone.

Installing it on a phone or tablet

It is not on the Play Store, so it installs the way any app from outside the store does. Android walks you through it; these are the three places it stops to ask.

• Open this page on the phone itself and press the download button. The file is about 17 MB.
• Open it from the notification or from Downloads. The first time, Android says the browser is not allowed to install unknown apps and offers a settings screen - turn it on for the browser, come back, and press install. You are allowing that one app to install this one, and you can turn it off again afterwards.
• Play Protect then says the app was not scanned, or that it comes from an unknown developer. Choose Install anyway. That warning is what Android says about every app that did not come from the store; the build is not signed by a registered developer yet.
• Open Palladium and give it a server: the address of the machine running it, or the whole invitation link somebody sent you.

Installing it on a television

A Google TV has no browser worth typing into, so the server hands the file over by a short code instead.

• Install Downloader from the Play Store on the television, and allow it to install unknown apps when it asks.
• On the computer running Palladium, open Settings - Install on a phone. It shows a five-character code and the exact line to type, which looks like 192.168.1.20:8765/i/AB12C.
• Type that line into Downloader with the remote. It fetches the app from your own server - the file never comes from here - and installs it.
• Play Protect asks the same question as on a phone. Install anyway.

After that

• The app updates itself from the Palladium server it is connected to. This page is not needed again.
• Uninstall it as you would any app; nothing is left behind on the phone but its own settings.

If your server has no copy of it

A server installed from the Windows installer carries the app and can hand it straight to a phone or a television. One running in Docker does not carry it. Its owner gives it one in Settings:

• Fetch it. One button. The server takes the published build from palladium.video, keeps it, and hands it out from then on. Nothing about the machine goes with the request.

Until that happens, the install page on that server says so plainly rather than offering a file it has not got.

Where a new version comes from

Updates travel down a chain, one link at a time, and each link only ever talks to the next one. Nothing skips to the end, and nothing on your side of it reports back.

1. palladium.video publishes a build. One installer, one app, one hash for each. This is the only machine here that anybody else's computer talks to, and only when it is asked.
2. Your server fetches it, when you say so. It checks what is published, shows you the number, and installs it on request - having checked the file against the published hash and refused it if they disagree. It sends nothing to get an answer: it reads a small file, the same one anybody can read.
3. The app updates from your server. Not from here. It asks the server it is connected to what build that server is carrying, and takes the app from it - over your own network, at home. A phone that knows several servers asks the one it is using first.
4. A second machine updates from the first. If you have one keeping copies, it follows the machine it copies from rather than the site, so a house ends up on one build without anybody visiting a page.

Which is why the app never asks palladium.video for anything: by the time it is installed, everything it needs is on a machine you own. The one exception is the very first download, if you took the file from this page rather than from a server.

Then

• The server, if there is not one running yet.
• What it does, in full.