cyroxx/private_health
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

reword architecture section

Browse Source
This commit is contained in:
Matthias Jacob
2026-02-27 02:47:46 +01:00
parent f9ee007a76
commit 55d0098699
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
README.md
View File

@@ -5,11 +5,11 @@ This project aims to create the necessary building blocks in order to allow coll
## Architecture
The architecture should use existing building blocks where possible.
For details, please see the diagram below. It shows existing apps (green), parts with only partial solutions so far (orange) and aspects which would need to be designed and developed mostly from scratch (red).
This architecture leans on proven, reusable components wherever possible.
Refer to the diagram below for an overview: it highlights mature apps in green, partially solved areas in orange, and gaps that require mostly new development in red.
At the moment, the [HealthConnect API](https://developer.android.com/health-and-fitness/health-connect) is seen as a central part for integration and synchronisation.
Supporting the HealthConnect API allows to integrate devices for which FLOSS app do not exist yet. It also makes the migration easier, since you can migrate step-by-step to a more privacy friendly stack.
At the moment, the [HealthConnect API](https://developer.android.com/health-and-fitness/health-connect) is remains a pragmatic choice for integration and synchronisation.
It lives on the user’s phone, encrypts data, and speaks schemas for dozens of vendors. That buys time for a gentle migration: you can keep your current wearable, pull data into a local store, and steadily replace proprietary parts as FLOSS apps/adapters mature.
However, alternative solutions to the HealthConnect API are more than welcome.