Repository navigation
Future of Noop ? #93
Description
Friends,
First of all, I wanted to thank ryanbr for taking over the reins of the app! It’s a program we all appreciate, and many of us use it every day.
I don’t know what direction he plans to take this project in from here :
- greater compatibility?
- more features?
- stability and polish?
I’d like to suggest we discuss these topics and also get the opinion of the app’s main developer.
For my part, I’m wondering: Is it necessary to keep using Liquid Today?
Personally, I think this design choice is a mistake and that the overall look is not as good as that of the original interface.
Shouldn’t we just drop it? Or at least drop one of these interfaces?
The discussion is open.
Reacted by Alvaro Machuca Recalde and Alexander Tarasov
Activity
ruedigermunz commentedon Jul 8, 2026
From a user point of view i would say both designs can be used and there are some who will prefer the old one and some who prefer the new one, but i would also prefer to focus on one design and not on two.
But the main goal should be to get all possible figures out of whoop4 and whoop5/mg, so on my point of view the focus should be on decoding everything what is possible, like spo2 like steps and stuff like that and
not focus on other wearables. Whoop was the game changer and first the prio should be on the decoding of those 2 straps.
Thanks for the ongoing development ryanbr! really cool that you continue and there are lots of people who are really thankful for that, so we are still able to use the whoops without sub!! Thanks!!
mohdarsal9-sudo commentedon Jul 8, 2026
Big thanks to ryanbr! for keeping this project alive.
Since it's a huge job, let's make sure they don't get burnt out doing it alone. I’m not a coder myself, but it would be awesome if those of you with the skills could team up to share the load.
Together we can move mountains.
kavemang commentedon Jul 8, 2026
As far as I can tell skin temp and SpO2 is not working yet from 4.0 so I would say stability and polish before new compatibility or features
pilleuspulcher-blip commentedon Jul 8, 2026
For me as user it's important to have a stable tracking and reading of all captured data of the Whoop 4. 0.
At the moment I have 2 Whoop 4.0 running side by side, connected to Whoop app and Noop app.
Workout detection is often at the same level, Noop needs more heart rate to jump in.
Sleep tracking often is equal, start and end spot on, sleep stages a bit different, but not much.
Thanks to @ryanbr for continuing the Noop project and to all other people who are participating with logs and ideas. 👍🙋♂️
sactyr commentedon Jul 9, 2026
Thank you to @ryanbr for continuing this project. I too would prefer for Noop to first track core metrics, probably in this order:
My 2 cents.
Android: our own WHOOP 4.0 raw SpO2 ADC on Health (#93)
Raw SpO2: align iOS/Android to full parity (#93)
Merge pull request #119 from ryanbr/ios-spo2-raw-93
iOS/macOS: surface WHOOP 4.0 raw SpO2 ADC on Health (ryanbr#93)
Release v8.5.0: changelog + version bump
exzanimo commentedon Jul 9, 2026
Thank you so much to @ryanbr and everyone involved for your hard work and for continuing to develop Noop; it truly means a lot to everyone who uses the app every day.
digitalerdude commentedon Jul 11, 2026
AI helped me find an alternative to Whoop in the first place and get the AltStore installed. I was already impressed by then, but once the project shut down, I started looking into it and wondered if there was some way I could help.
I can't code, but I love participating here and supporting the project—at least through "vibe coding." Thanks, @ryanbr, and best regards to everyone. 🫶
iOS/macOS: surface WHOOP 4.0 raw SpO2 ADC on Health (ryanbr#93)
Android: our own WHOOP 4.0 raw SpO2 ADC on Health (ryanbr#93)
Raw SpO2: align iOS/Android to full parity (ryanbr#93)
Merge pull request ryanbr#119 from ryanbr/ios-spo2-raw-93
Release v8.5.0: changelog + version bump
Health: Hearth flat-ink header + Cardiac/Overnight group cards