← Back to catalogue
Logo de PhysioApp
CONNECTAPP / APPLICATION

PhysioApp

Tablet app for physiotherapists and clinics: patients, professionals, clinical reports and internal receipts, using local data.

Kotlin MultiplatformAndroidiPadOffline-first
01 / OVERVIEW

Features

  • Patient records with signatures and consent history
  • Professional registration, search and archiving
  • Clinical reports with version history and PDF export
  • Internal receipts with yearly numbering and payment tracking
  • Local sign-in, password recovery and inactivity lock
  • Encrypted backups and restoration on another tablet

Designed for tablets

PhysioApp is for physiotherapists and clinic staff managing their work on an iPad or Android tablet. It works offline, without server accounts or cloud services.

The interface adapts to portrait and landscape, iPad Split View and Android multi-window. Home provides eight shortcuts for registering and finding patients, professionals, reports and receipts. It is not designed for phones.

Patient and professional records

Patient records include identification, contact details, notes and handwritten consent signed by the patient or a legal representative. Signature history and the version of the consent text are retained. The included consent text is provisional and requires adaptation and review before clinic use.

Professional records include identity, association and licence number. Searches use one criterion and archived records can be restored. Several accounts can share a tablet: every professional can see the patients stored on that device.

Reports and PDF receipts

Each clinical report has a unique code and records its author. Only the author can edit or annul it with a reason; previous versions are retained. Reports are never deleted and can be exported to PDF.

Receipts include sequential yearly numbering, a concept, an amount and paid or pending status. Only the author can change payment status or void them; corrections require voiding and issuing another receipt. They are internal payment receipts, not tax invoices.

PDFs are generated offline and can be saved or shared through system options. They are not password-protected: exported data leaves the protection of the app.

Local access and data protection

The SQLite database is encrypted with SQLCipher and its key is stored in Android Keystore or iOS Keychain. According to the README, the app uses no backend, analytics or telemetry, and Android declares no Internet permission.

Registration includes a recovery code shown only once. Sessions close after five minutes of inactivity and sign-in is locked for five minutes after five failed attempts. Settings allows password changes and recovery-code regeneration.

Android blocks screenshots and recordings. On iPad, content is hidden in the app switcher and during recording or screen mirroring; the operating system does not allow apps to block screenshots.

Backups and moving to another tablet

Settings can create a full backup encrypted with its own password and lets you choose where to save it. The app reminds you if no backup exists or the last one is seven days old. Backups are manual, without automatic synchronisation.

A backup can restore data on another tablet. Restoration replaces all content, including accounts; it cannot merge data and requires a compatible database version. The backup password is not stored and cannot be recovered.

Technology and validation status

Built with Kotlin Multiplatform and Compose Multiplatform, using modular architecture, MVI, Koin and SQLDelight. Source code is published under Apache 2.0 and third-party licences can be read offline in the app.

The README documents automated logic, UI and encryption tests on Android and the iOS simulator. Full manual validation on real tablets, screen-reader checks and deployment review remain pending. The project remains pre-alpha, with no published releases or security audit.

Known limitations include losing unsaved forms when a session ends, PDF character restrictions and possible text learning by the system keyboard. Read the README for current details.

02 / PRIVACY

Data and privacy

Local data, encrypted backups and privacy safeguards. Full manual validation on real tablets remains pending.

03 / READ BEFORE USE

Important considerations

Pre-alpha, without a security audit and pending full manual testing on real tablets. The README states that this version must not be used with real patient data. Deployment requires reviewing the provisional consent, receipts and backup arrangements with the clinic.

For technical setup and up-to-date requirements, read the repository README.