DEV Community

Cover image for Introducing PhysioApp: Building an Open Source App for Physiotherapists ๐Ÿฉบ
Manuel AF
Manuel AF

Posted on

Introducing PhysioApp: Building an Open Source App for Physiotherapists ๐Ÿฉบ

Exploring cross-platform development, software architecture, and the importance of building healthcare tools with real professionals.

Hey DEV Community! ๐Ÿ‘‹

What if we could combine open-source software, mobile development, and healthcare to build tools that genuinely help professionals?

That's the idea behind PhysioApp, a project I'm developing as part of ConnectApp, my independent initiative focused on creating reusable open-source software.

PhysioApp is designed for physiotherapists and physiotherapy clinics, with a tablet-first approach targeting Android tablets and iPads.

The goal is to explore a practical application that could help professionals organize their daily work while prioritizing usability, maintainability, and responsible handling of sensitive information.

But there's something particularly important about this project:

I don't want to develop a healthcare application without listening to the people who would actually use it.

๐ŸŽฏ What is PhysioApp?

PhysioApp is an application intended to support administrative and clinical workflows in physiotherapy practices.

Its planned capabilities include:

  • ๐Ÿ‘ค Patient and professional management.
  • ๐Ÿ“‹ Patient records and treatment-related information.
  • ๐Ÿ—“๏ธ Organization of clinical activities.
  • ๐Ÿ“„ Reports and administrative documents.
  • ๐Ÿ’พ Data management and backup workflows.
  • ๐Ÿ“ฑ An interface designed for tablet interaction.

These features form the project's development direction and should not be interpreted as a claim that every workflow is already production-ready.

The application is currently in an early development and evaluation stage.

๐Ÿ’ป Exploring cross-platform development

One of the technical challenges behind PhysioApp is designing an application for different tablet platforms without unnecessarily duplicating business logic.

The project explores Kotlin Multiplatform as a way to share appropriate parts of the application while respecting platform-specific requirements.

That creates interesting architectural questions:

  • Which components should be shared between Android and iOS?
  • How should application logic be separated from user-interface code?
  • How can validation remain consistent across platforms?
  • How should data ownership and persistence be handled?
  • How can we maintain readable, testable, and extensible code?

For me, these questions are just as interesting as building the interface itself.

๐Ÿ—๏ธ Software architecture matters

PhysioApp follows the engineering philosophy I try to apply throughout ConnectApp.

That includes exploring principles such as:

Clean Architecture: separating business rules from frameworks and infrastructure.

SOLID: promoting clear responsibilities and manageable dependencies.

Clean Code: keeping implementations understandable and maintainable.

Testing and validation: checking expected behavior rather than assuming that an application is reliable simply because it runs.

These practices are particularly important when developing software intended for professional environments.

An attractive interface is valuable, but it cannot compensate for unreliable behavior or inadequate data protection.

๐Ÿ” Privacy and healthcare software

Physiotherapy applications may handle particularly sensitive personal information.

That makes privacy and security fundamental design concerns, not optional features.

Some of the areas that require careful attention include:

  • Appropriate authentication and access control.
  • Secure local data storage.
  • Protection of backups and exported documents.
  • Data minimization.
  • Clear handling of patient information.
  • Regulatory requirements and professional workflows.

PhysioApp is not currently validated for production use with real patient data.

Any testing at this stage should take place with fictional or appropriately anonymized datasets.

Before real clinical deployment, the application would require appropriate security, privacy, functional, and regulatory assessment.

Open Source is not a substitute for those responsibilities.

๐Ÿ‘ฉโ€โš•๏ธ Why professional feedback is essential

One of my goals is to involve physiotherapists in the project's evolution.

Developers can implement interfaces, data models, and business logic, but healthcare professionals understand the practical details of their daily work.

I would particularly value feedback on:

  • How easily professionals can navigate the application.
  • Whether the proposed workflows reflect real needs.
  • Which features could simplify administrative tasks.
  • What should be changed or removed.
  • Which accessibility and usability improvements matter most.

I believe that collaboration between developers and professionals is essential to creating software that is genuinely useful.

๐ŸŒ Why Open Source?

PhysioApp is also an opportunity to explore how open-source development can benefit professional organizations.

Making source code available can encourage transparency, learning, external review, and collaboration.

It can also allow others to propose improvements and adapt software under the terms of its license.

However, my view is simple:

Open Source does not mean second-class software.

Free and open-source applications should aim for the same professionalism, quality, and reliability expected from commercial alternatives.

That responsibility becomes even more important when software is designed for healthcare.

๐Ÿค Looking for feedback and collaboration

I'd love to hear from:

  • Physiotherapists interested in improving digital workflows.
  • Kotlin and mobile developers working with cross-platform architecture.
  • UI/UX designers experienced in tablet applications.
  • Software engineers interested in privacy, security, and maintainability.
  • Students looking to learn from a real-world development project.

PhysioApp is still evolving, and constructive feedback can help shape its direction.

If you're a physiotherapist, I'd love to know:

What is the most frustrating part of the software you currently use in your daily work?

And if you're a developer:

What would you consider the biggest technical challenge when building a cross-platform application for a healthcare environment?

๐Ÿš€ Part of ConnectApp

PhysioApp is one of the projects I'm developing through ConnectApp, an independent initiative I created to explore software engineering, open-source collaboration, privacy, and responsible development.

My goal is not simply to publish applications.

It's to build useful software, share knowledge, learn from feedback, and continuously improve the quality of what I create.

๐ŸŒ ConnectApp: https://www.connectapp.es

๐Ÿ’ป GitHub: https://github.com/ManuelAf-ConnectApp

Let's build open-source software that combines technical quality with real-world needs. ๐Ÿš€

Top comments (2)

Collapse
 
ahmedznouda profile image
Ahmed ZNOUDA •

Saying up front that it isn't validated for real patient data is the right way to start a healthcare project, and going to physiotherapists before building is the step most of us skip.

Two things we learned shipping a health-related app on Google Play that are worth planning early:

  • On Play, a health app may have to be published from an organisation developer account, not a personal one. Ours was rejected for that, and getting the D-U-N-S number it requires takes time.
  • Exports are where data leaves your control. We generate the PDF report on the device and hand it to the system share sheet, nothing is uploaded, but once it's sent to a chat app it's gone. A clear line on the document about what it is and isn't, and keeping it to what the reader needs, does more than encryption at that point. On Android, also check android:allowBackup, or the local database can end up in the user's cloud backup.

Will one tablet be shared by several therapists in a clinic? That changes the access-control design a lot.

Collapse
 
connect_app_es profile image
Manuel AF •

Thank you so much for sharing your experience and these valuable insights!

This is exactly the kind of feedback I was hoping to receive when sharing PhysioApp with the community.

Youโ€™ve raised two really important points, especially regarding Google Play's organisation account requirements and the challenges of managing sensitive data once it leaves the application.

I completely agree that privacy doesn't end with encryption. Generating documents locally, minimising the information they contain, and clearly communicating their purpose and limitations are essential considerations.

I'll also review Android's allowBackup configuration and the relevant backup and data extraction rules to ensure that sensitive information isn't unintentionally included in cloud backups.

PhysioApp is still in an early development stage, so your experience is extremely helpful in identifying potential issues before moving towards real-world validation.

My goal isn't just to build a functional application, but to develop something trustworthy, maintainable, and genuinely useful for physiotherapy professionals.

Thanks again for taking the time to share what you've learned. This is what makes the open-source community so valuable!