On-device storage needs a recovery plan
PhysioApp stores its data in an encrypted local database without a synchronisation server. That makes protecting the tablet and recovering information if the device becomes unavailable two separate concerns.
The device database uses a key stored in Keystore or Keychain. According to the README, the app’s own backups use an independent password, allowing restoration on another tablet without relying on the original device key.
The app remains pre-alpha. Its documentation states that this version must not be used with real patient data. The following describes documented behaviour that can be explored with fictional records.
Creating a backup
The backup option in Settings asks for a password and opens the system picker to choose where to save the file. It contains the whole database, rather than a selection of patients or a PDF export.
The application does not store this password and cannot recover it. Keep it separately from the file. Home shows a reminder if no backup exists or the last one is seven days old, but the reminder does not create a backup automatically.
Keeping the file only on the same tablet does not address losing that device. Choosing the destination and safeguarding the file are part of the procedure whoever adapts the app needs to define.
Restoration replaces existing data
Restoring from Settings requires the file, its password, the sign-in password and confirmation. Successful restoration replaces the tablet’s data, including accounts, and ends the session.
On a tablet without accounts, the sign-in screen offers a restore option. There is no merging of the backup with newer records on the device. Restoration is not an import of selected documents.
Compatibility matters too: the README limits restoration to a compatible database version. A backup should not be assumed to work with every future release.
A useful test with fictional data
Before relying on this workflow, a practical check can include:
- Creating fictional records and generating a backup.
- Confirming that the file was saved to the chosen destination.
- Restoring in a test environment and checking records and accounts.
- Verifying that everyone understands what restoration replaces.
The README documents automated encryption and backup tests, while complete manual checks on real devices remain pending. Automated tests do not replace validation of the intended use.
Backups and PDFs serve different purposes
A PDF report is a document for reading or sharing; it cannot rebuild the application’s accounts and records. The encrypted backup is intended to restore the entire database.
Read the PhysioApp overview and project README for requirements, warnings and limitations before preparing an adaptation.