The state of NOOP: where the project stands, what to expect, and how it gets built 🤔
I want to set out clearly where NOOP stands today, what you should expect from it, and what it is going to take to get this where we all want it to go. If you are new here, or you have just downloaded it expecting a finished product, please read this properly. It matters, and it will save us both a lot of frustration.
What NOOP is
NOOP is a free, open, on-device companion for your WHOOP and a growing range of other straps, watches and bands. Everything runs locally on your phone or your Mac. There is no account, no cloud, no subscription, no telemetry, and nothing you record ever leaves your device. It is built in the open by a small community, and every line of it is there for you to read, use, and improve.
That is the heart of it, and that part will never change.
What NOOP is not, yet
It is not a finished product. It is not a commercial app. It is not a polished, guaranteed, set-and-forget replacement for WHOOP, Oura or Garmin that you can lean on without a second thought. It does not come with a support desk, an uptime promise, or a roadmap that lands on a fixed date.
If what you need today is reliability you never have to think about, NOOP is not that yet. I believe it becomes that. It is not that right now, and it would be wrong of me to let you think otherwise.
Where we actually are: early, active development
NOOP is being built in real time. That is genuinely difficult, slow work, and it means the app is in constant motion. Setting your expectations straight here is the whole point of this post.
You should expect:
- 🔄 Frequent updates, sometimes several in a single day.
- 🐞 Real bugs. Things that work today and break tomorrow, then get fixed the day after.
- ↩️ The occasional regression, where a fix for one thing briefly unsettles another.
- 🧪 Features clearly labelled experimental, because they are not proven yet and we will not pretend they are.
- 📐 Numbers and screens that change shape as we learn what is actually correct.
- 🐢 Slow, deliberate progress on the hardest parts, because rushing them produces data you cannot trust.
None of that is the project failing. That is what building something this ambitious, in the open, actually looks like from the inside. If you are comfortable with that, you are in exactly the right place. If you are not, that is entirely fair, and it may be worth checking back in a few months when more of it has settled.
The work going on right now
This is a deliberate, organised effort, not something thrown together and abandoned:
- 🔋 A dedicated battery-testing group is being set up, because strap battery behaviour is subtle and only careful testing across real devices over real time will get it right.
- 🎨 A UI and UX testing group, to make sure the app does not merely work, but feels right to live with every single day.
- 😴 Sustained work on the sleep algorithms, which is some of the most demanding work in the entire app. Getting sleep staging genuinely accurate, from raw signals, on your device, is hard, and we are not going to fake it to look finished.
These things take time. I would far rather move at the pace that gets them right than ship something that looks impressive and quietly misleads you about your own body. That is a line I will not cross.
The orchestra, and why this takes time
The clearest way I can describe my role is this: I am stood at the front of an orchestra with the baton. The musicians are extraordinary, contributors writing code, people submitting strap logs, people testing corners I could never cover on my own. But you do not pull a full orchestra into a finished symphony in a week. We are in rehearsal. Some sections are tight. Some are still finding their timing. My job is holding the whole thing together and pointed in one direction while every part comes up to standard.
It will not all sound right yet. That is the nature of rehearsal, not a fault in the players. The performance is coming, and it will be worth the wait, but the wait is real and I am not going to pretend it away.
How NOOP actually gets built: GitHub is the engine
This is the part I most need you to take on board. NOOP does not improve because one person codes in isolation. It improves because of you, through GitHub. There are three ways to be part of that, and each one genuinely shapes the app.
1. Report bugs, properly. 🐛 Not in a passing Reddit comment, and not as a vague "it is laggy". File it on GitHub Issues, with a strap log attached. There is a button in the app to capture one, and the template walks you through exactly what we need. I cannot fix what I cannot see. A clear report with a log is the single most valuable thing you can give this project, and a large share of every release comes directly from one person taking a few minutes to file one well. The dashboard performance fix that just shipped came from precisely that: one person, one clear report, one strap log. That is the entire loop, and it works.
➡️ Report a bug · All open issues · How to grab a strap log and report it
2. Send a pull request. 🔀 A great deal of what is in NOOP came from the community writing code. We review every single one ourselves, verify it, and reimplement it cleanly rather than merging blindly, but the ideas and the fixes are yours. If you can code, this is the most direct way to build the thing you wish existed.
➡️ Open pull requests · Contributing guide · Roadmap and where we need help
3. Take part in the wider effort. 💬 The testing groups, the discussion, the feedback, it all lives in the community and it all feeds straight back into what gets built next.
➡️ Discord · r/NOOPApp
And if you are here simply to download the app, please understand why it lives on GitHub in the first place. That is not an app-store listing. It is a development repository. You are taking a work-in-progress out of the exact place we are actively building it. That is a good arrangement, free, open, and yours, but the understanding that comes with it is firm: you are an early tester in a build that changes constantly, not a customer buying a finished product off a shelf. Treating it as the latter is where the disappointment comes from, and I would rather you treat it as what it is.
Where this is heading
The destination has not moved. NOOP is becoming a genuine, reliable, on-device alternative to the subscription wearable apps, one that respects your data completely and costs you nothing. We are not there yet. We get there by doing the hard parts properly rather than quickly, and by everyone who uses it taking part in making it better.
That is the deal. It is a serious project with a serious goal, and it is going to take time, patience, and all of us pulling in the same direction.
Everything in one place
| 🏠 Repository | https://github.com/NoopApp/noop |
|---|---|
| 🪞 Mirror (if GitHub is ever down) | https://noop.fans |
| 📥 Download and all releases | https://github.com/NoopApp/noop/releases |
| 📌 Start here (FAQ and how to report a bug) | #470 |
| 📖 Wiki home | https://github.com/NoopApp/noop/wiki |
| ❓ FAQ | wiki/FAQ |
| 🚀 Getting started | wiki/Getting-Started |
| 📱 iPhone install (sideload or build from source) | iPhone guide |
| 🩺 No data or blank scores? | Fix-it guide |
| 🐛 Report a bug | New issue |
| 🔀 Pull requests | Open PRs |
| 🙏 Roadmap and help wanted | #132 |
| 💬 Discord | https://discord.com/invite/nHK9FHczu |
| 💚 Support the project | docs/DONATIONS.md |
What I am asking of you
Be patient. Be early. Use it knowing exactly what it is. When something breaks, report it properly, with a log, on GitHub. If you can write code, send a pull request. Every issue you raise carefully is a problem solved for the next person, and every contribution moves the whole thing forward.
This is not a finished app, and I am not going to dress it up as one. It is a serious, long-term effort to build something genuinely worth having, in the open, for free, and it is going to take real time and real commitment from all of us. If you are here for that, you are exactly who this is for. Thank you for being part of it while we build it properly.