I wear a WHOOP. I've coached people on movement and sleep for many years and I still can't answer that question for myself. The algorithm is locked. You get a number, you trust it, you stop there.
When we built Open Wearables, we decided the scoring layer should work differently. Sleep Score and Resilience Score shipped in v0.5 - every coefficient, every threshold, every weighting is in the repo and you can fork them, tune for endurance athletes or elder care or clinical populations. Moreover, you run them on your own infrastructure and the same algorithms feed the MCP layer so AI coaching can cite the actual data behind a recommendation instead of approximating.
Been on Apple Watch + Bevel for ages and still feel like I'm only using maybe 20% of what my data could actually tell me... definitely the right move. Love the open source approach, too!
Also full disclosure — I know the team behind this and they don't ship things halfway. Congrats guys, lfg!
Open Wearables
@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.😄
Open Wearables
@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
Feels like early days, but the direction is very promising. Excited to see how the API gets used by the builders.
Open Wearables
@himani_sah1 It is early days, and we're upfront about that. The use cases already showing up are the interesting part: clinical teams auditing algorithms, coaches normalizing HRV across devices, AI builders wiring the MCP server into health coaching tools. We'll be watching what gets built.
@himani_sah1 Early days, yeah - but it's already a full engine :D
Love the positioning here. Feels like “Stripe for wearable data” is spot on 😊
Open Wearables
@zerotox The Stripe analogy fits the data layer well:) Where we go further is that Stripe stops at the transaction: we also compute what the data means, with open algorithms you can audit and tune. Health intelligence on top of the plumbing, not just the plumbing.
@zerotox Interesting take, thank you for your kind words!
This is great! Next thing we need is standardized API that the vendors commit to adopting. The Bluetooth heartrate profile and Generic Health Sensor profiles were a promising start but haven't lived up to their potential.
Open Wearables
@richieoh Agreed Richie, the Bluetooth SIG profiles (HRP, GHS) had the right idea on paper but vendors have zero incentive to converge, differentiation and lock-in are part of the business model, so a pragmatic abstraction layer is the only thing that ships in our lifetime.
Voted and bookmarked. We're a small product studio in Krakow and this goes on the "evaluate for our next health client" list immediately. The Momentum team has been doing solid work in this space for a while now.
@jakub_mitka I’m looking at it in a similar way, something to evaluate on the next relevant project 👍
Nice to see someone from Krakow thinking about it in a client context too. It feels like this could genuinely simplify working with health data, if it delivers on the promise. I’ve also come across the Momentum team before - good to hear they already have a solid track record in
@jakub_mitka Jakub - appreciate the vouch. Product studios with multiple health clients are honestly the cleanest fit for this - one shared layer beats rebuilding integrations for every project.
@jakub_mitka Love to see this added to the studio toolkit! Having a unified API ready to roll out for future health clients is a massive time-saver for agencies. Greetings to Krakow! 👋 And I completely agree-the Momentum team has definitely earned their strong reputation in the healthtech space.
I looked at this for maybe 30 seconds and then went to star the GitHub repo. The combination of open algorithms and zero per-user pricing is something I've been waiting for someone to ship.
Open Wearables
@wszubryt that means a lot, thank you
the pricing thing is something we felt strongly about from day one. per-user fees at scale just punish success - you build something that works, your costs explode. doesn't make sense for health apps especially
open algorithms matter too because health scoring has been a black box for too long. sleep score of 73 - why? what changed? you deserve to know
star appreciated, hope it earns it as we keep building
@wszubryt Thank you so much! We all love github stars!
The world where you are paying for a wearable and often a subscription on top of it while still not really owning your (often really important) data has been waiting for a proper disruption for a while. I am glad it came from you. Fingers crossed from a fellow Wrocławiak 🤞
Open Wearables
@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 :)