Android app¶
The Android app puts every BombVault server of your group on your phone. It starts on a list of your servers with the activity log of all of them on top, the same lines the overview shows, and opens the phone view of whichever server you tap. The app backs nothing up itself.

Getting the app¶
- Settings, Apps: the Android app's card offers the APK for the release your server runs, with a QR code to scan from the phone, and links the F-Droid listing.
- APK: every release has
bombvault-android.apkon its release page, and this link always downloads the latest build. It needs Android 10 or later, and Android asks once whether the app you open the file with may install apps. - Google Play: BombVault on Google Play. It is signed with the same key as the APK, so either one installs over the other.
- F-Droid: BombVault on F-Droid. F-Droid builds the app from the source and signs it with its own key, so a new release reaches it a few days later. To switch between the F-Droid app and the APK, uninstall the other one first.
Pair the app with servers on version 9.7.0 or later. A server on an older version can be in the same group, but it shows the phone as a plain instance, and the app reads that server's activity only after a sign-in.
Pairing by QR code¶
- On any server of your group, open Settings, Pairing and choose Show phrase. The twelve words appear with a QR code beside them.
- In the app, tap Scan QR code and point the phone at the code. You can also paste or type the words.
- The app lists the servers of that group before it saves anything. Add all adds every one of them.
The phone then joins the group like another instance. It reads what runs on each server through the group without a sign-in, at home directly and away from home over the relay. How the group itself works is described under Pairing instances.
The app joins the group through the relay, also at home. If your instances use No relay, pick one under Settings, Pairing before you scan the code.
Away from home¶
The app first tries a server at its own address. When that does not answer, as on the mobile network, it opens the server's interface through the group's relay instead. A server of the group whose address the app does not know yet opens the same way. If neither the address nor the relay answers, the start screen says so on the server's card.
Over the relay the page reaches what a paired phone reaches at home, described below. Signing in with the password and saving files work only at the server's own address. Progress bars update every two seconds instead of continuously. The interface's files stay on the phone after the first visit, so later visits load faster. A server older than 10.0.0 opens only at its own address.
The app takes an answer only when the server signed it with the key the app pinned when it first met that server. If the server later answers with another key, the start screen shows the new key's fingerprint, and the page opens only after you trust it.
Switching servers¶
With a server open, the top of its overview shows the server's name, with a back arrow before it. The arrow leads to the app's overview, the start screen, which lists every server the app knows with its state: Connected, Not connected, Sign-in needed or Check certificate. A server of the group that does not answer is Inactive, in grey, with when the group last saw it, and one the app has not heard from yet says Checking. Each time it connects, the app reads the group's list from one of its instances, so an instance it never met on the relay, such as one that was shut down when the phone joined, is listed too. Tap another one there to open it, directly at home and through the relay otherwise.
Signed in on a paired phone¶
A phone paired with your group opens each of its servers already signed in. Before it loads a page, it asks that server over the group for a session, and a server hands one only to a member that is a phone.
A paired phone does not get everything a password does. Its session reaches a fixed list of what the app shows: the overview, the runs and the activity log, the backups to look at, start and restore, the anomalies to read and the Instances page to look at, without the received repositories and pull sources of its members. Storage locations and commands come back with their addresses and secrets removed. A restore that replaces the original backs up the current state first. A restore into a folder goes into a new folder inside the restore folder set under Settings, Restore, and the window offers no other. Keys, the recovery kit, key deposits, settings and deleting backups stay with a sign-in at the server itself, and everything else answers that it needs that sign-in. Over the relay the same list applies, also on a server without a password.
The switch for this is Phones can pair with the group's twelve words on the Android app card under Settings, Security. A password reset turns it off and signs every phone out, until you turn it back on there.
Certificates¶
A self-signed certificate is trusted once by its SHA-256 fingerprint. When the server later shows a different one, the app warns you and opens it only after you trust the new certificate.
The phone on the Instances page¶
The phone gets its own card on the Instances page of every server in the group, marked as an Android app and named after the name you gave the phone. It has no scorecard because it backs nothing up. Remove takes it off the page and ends its session at once, as does switching off Poll this instance under Monitoring in its details. The phone still knows the words, so it shows up again when its app opens, but switched off, and it gets no session until someone switches it on. For a lost phone remove its card on every server, or switch Phones can pair with the group's twelve words off under Settings, Security, or let every instance Leave group and pair them again with new words.
A phone paired before 10.0.0 starts signing its calls on its first visit after the update, and each server keeps the first key it gets for the phone. If someone else who knows the group's words gets there first while the phone is offline, that server turns the phone away from then on, and the app can no longer open it over the relay. To fix this, sign in to that server in a browser, choose Forget key on the phone's card on the Instances page and then Confirm forget, and open the app again. The server takes the phone's own key on its next call. If the phone is turned away again, someone else has the words: let every instance Leave group and pair them again with new words, as for a lost phone.
Nodes¶
Nodes are looked after in the web interface. A paired phone's session does not reach them, so the app shows no node cards on the Instances page, no Nodes card on the overview and no node sections under Backups, and Add node answers that it needs a sign-in at the server itself. Open the server in a browser and sign in with the password to add a node, change where its backups go or restore one of its entries.
Settings¶
The gear beside the plus opens the app's settings:
- the language, and the name the phone shows on the Instances page (empty means the phone's model),
- the look, which follows the first server in the list until you set your own, and animations, which have a setting of their own,
- a report to copy when you report a problem. It contains no address, name or phrase,
- the About card with the privacy policy,
- Remove all servers, which removes every server from the app and leaves the group. Every server the phone still reaches takes it off its Instances page.
Downloads and uploads¶
Exports, recovery kits, flash ZIPs and database dumps land in the phone's Downloads folder, as they would from a browser. A settings import opens the phone's file picker. Over the relay no file is saved. Open the server at its own address for that.
On a touch screen¶
Nothing hovers under a finger, so a control dims while it is held, and a button with a brand logo lights up in its brand colour until the finger lifts. A long press on a button counts as a slow tap and opens no link menu. A tap on a greyed-out button shows why it is greyed out, until you tap somewhere else.
In a browser instead¶
Chrome and Edge can install BombVault's web interface as an app in its own window, on a phone as on a computer. Nothing is cached, so an update shows at once.
Privacy¶
The app has no accounts, no advertising and no analytics, and it runs nothing in the background. Its privacy policy lists what it stores and what it sends where.