Open Wearables - Open infrastructure for wearable-powered health products.
by•
Build personalized health products with one API for every wearable. Access wearable data, open health scoring algorithms, and structured context your AI can reason with. Self-hosted, open-source, MIT licensed.
Spent some time in the repo before commenting – looks like the data model is actively evolving, which makes the question I had even more relevant. The docs frame ingestion as either Cloud-based (OAuth provider) or SDK-based. Is there a planned third pattern for sources that fit neither – e.g. a desktop client generating data locally and POSTing records via the public API directly? Technically nothing seems to block it, but curious whether that's intended usage or off-pattern.
Have a project sitting in this exact gap, so watching with interest. Aware it's early-stage.
@piotr_sobusiak Got it, thanks Piotr – that's what I needed to know. Will dig into the POST endpoints 🙌
Report
My partner uses Whoop and I use Apple Watch and we've argued more than once about whose recovery score methodology makes more sense 🤔🧐 genuinely excited something like this exists now 😃
Report
open infrastructure in health is a brave bet. the value is obvious but the regulatory complexity is brutal. curious whether you're seeing builders use this for consumer products more
@piotr_ratkowski Congrats on the launch! Such nice work. I have a question, though. How do you handle data privacy and consent when pulling health data from multiple wearable providers, especially for teams that need to stay compliant?
Replies
GlowPulse
Spent some time in the repo before commenting – looks like the data model is actively evolving, which makes the question I had even more relevant. The docs frame ingestion as either Cloud-based (OAuth provider) or SDK-based. Is there a planned third pattern for sources that fit neither – e.g. a desktop client generating data locally and POSTing records via the public API directly? Technically nothing seems to block it, but curious whether that's intended usage or off-pattern.
Have a project sitting in this exact gap, so watching with interest. Aware it's early-stage.
Congrats on shipping 🚀
Open Wearables
@zhuzhavladislav not sure if that's the case, but we have data generator built in the Open Wearables dashboard - you can see it in action in our docs: https://openwearables.io/docs/dev-guides/seed-data-generator#seed-data-generator
And like you've mentioned - it could be also done by any client and using POST endpoints to store data in OW
GlowPulse
@piotr_sobusiak Got it, thanks Piotr – that's what I needed to know. Will dig into the POST endpoints 🙌
My partner uses Whoop and I use Apple Watch and we've argued more than once about whose recovery score methodology makes more sense 🤔🧐 genuinely excited something like this exists now 😃
open infrastructure in health is a brave bet. the value is obvious but the regulatory complexity is brutal. curious whether you're seeing builders use this for consumer products more
Cool! Is there HIPAA compliance?
Do they have an explainer video already or not?
@piotreksedzik
@piotr_ratkowski Congrats on the launch! Such nice work. I have a question, though. How do you handle data privacy and consent when pulling health data from multiple wearable providers, especially for teams that need to stay compliant?