Open Wearables - Open infrastructure for wearable-powered health products.

@zuzanna_gutkowska Thanks for following along! 😊 If you like this you may also like The Science Behind Wearabes where we dive much deeper into that: https://thesciencebehindwearables.substack.com/

@zuzanna_gutkowska Do you have your favourite Open Wearables linkdin posts series? Just curious which ones reached you ;)

@itsluo That's the exact problem we keep seeing. Six to twelve months of OAuth integrations before you can ship anything meaningful kills most indie health projects before they start. Railway deploy in five minutes was a deliberate choice.

@itsluo Does the `indie health app` label fits to you company? :)

@roopreddy Batch-based right now, which reflects the underlying provider APIs: most wearables sync to their cloud on a schedule rather than streaming continuously. Some providers like Whoop expose webhooks, and we're looking at event-driven support for those. True real-time would require lower-level device access that most providers don't offer yet.

@roopreddy Thanks! This depends also on the providers how often they push data but as soon as these data reaches Open Wearables, there are webhooks you can use to push data to your backend real-time - here is more info about it: https://openwearables.io/docs/api-reference/guides/webhooks#outgoing-webhooks-open-wearables

@roopreddy To not repeat afer other, I can tell that FIT files supports is also planned, so it can changed how we fetch data to Open Wearables.

@jacksonburch Breathing + HRV + respiratory rate is a nice fit for the data model, all three are surfaced across most providers (Garmin, Oura, Whoop especially). If you give it a spin, drop into Discord with whatever you find tricky, happy to help unblock. Good luck with TryBreathing.

@jacksonburch Jackson - group breathing with live biometrics is genuinely one of the more interesting use cases I've heard today. The latency tradeoffs across providers are real (some are near-real-time, others poll on

intervals) - Piotr or our infra folks can dig into the specifics on Discord. Either way, that sister site sounds like exactly the kind of thing this stack was built for.

@jacksonburch I would suggest to check our docs. We have there a coverage matrix of which data types are supported.

@piotr_karwatka Thanks Piotr, "data bus for health/wearables" is a sharp framing, the standardization gap is exactly what kept biting us across client projects until we decided to just open-source the fix. Appreciate the support 🙏

@piotr_karwatka FInger crossed, thanks!

@abod_rehman Thanks for the kind words!

@abod_rehman Some providers (Apple, yeah, it's about you!) forced us to keep an eye on that issue early ;)

@abod_rehman and good to see this open sourced as well!

@k_waraksa The 20% feeling is more common than people admit. Most apps show you the raw numbers and leave the interpretation to you. Thanks for the kind words and for vouching, Chris. We'll try not to embarrass you.😄

@k_waraksa Bevel user here too, by the way. Great product, but still a long way to go on turning that data into something genuinely actionable. Appreciate the support, lfg 🚀

@k_waraksa Chris - that 20% number is real. I run 3 platforms across my own training and still feel like half the signal is locked behind some "open the other app" wall. Vouching means a lot today. Cheers 🙏

@k_waraksa Thanks for the recommendation! :D

@michal_wlodarczyk1 yes we do, each algorithm of open wearables is open and can be audited. Our Health Science Lead also runs her own substack in which she will also explain the details behind algorithms.

https://thesciencebehindwearables.substack.com/

@michal_wlodarczyk1 But to clarify that - we don't have an access to the Oura's alghoritms, nobody does. But our algorithms are accessible in our Github repo. They even have separate directory, so it's easy to find and analyse them.

@michal_wlodarczyk1 That’s a good instinct — “readiness” scores feel objective until you realize they’re really just weighted models over a handful of signals.

@michal_wlodarczyk1 As a running coach, this transparency is exactly what I've been waiting for. When athletes ask me "should I train hard today?", a black-box score doesn't help me make the call but being able to see what signals are weighted and why changes everything. Trust in the data = trust in the decision :)

@gregrog Thank you so much :)

@gaba6ool fellow Wrocławiak! that's unexpected and appreciated 🤞

you nailed it - people are paying twice and still don't own anything. the data is the product and somehow that got normalized

glad we could represent Wrocław on Product Hunt today haha

@gaba6ool That was frustrating for us as well. That's why Open Wearables has been created :)