NOOP is gone, so I’m rebuilding it. Here is the plan.

Screenshot of my WIP NOOP fork.

We all saw the shutdown post. It’s a shame, but honestly, the writing was on the wall. The project was struggling to stay upright, and the maintenance pressure eventually became too much for the original developer.

But the idea, giving people actual control over their own health signals, is still a good one. I don't want to let that disappear.

I’m taking the source code, but I’m not just patching it. The original app had serious architectural debt. It was laggy, bloated, and felt more like a tech demo than a daily tool. I’m currently stripping that back and rewriting the core logic from scratch to make it stable and fast.

The goal here is simple:
I’m building a clean, performance-first health tracker. As you can see in the screenshot I attached, the design is focused on data at a glance. No hidden menus, no confusion. Just the numbers that help you decide when to rest and when to push.

How I’m avoiding the burnout trap:
I’ve seen what happened with the original NOOP, and I’m setting hard boundaries from day one.

1. Keep the scope tight: This is not an "everything" app. It will only support WHOOPs for the foreseeable future. I am ignoring feature requests that add bloat. I am focusing on core health metrics. If it doesn't serve that specific purpose, it isn't going in.
2. Build for reliability: I am not taking shortcuts with the code. If the architecture is solid, the maintenance overhead stays low. That means less vibecoding and more effort.
3. Transparency: I’m doing this as a project I actually use. I’m not promising the moon. If I’m at capacity, I’ll say so.

I need your input on two things:

• What was the biggest dealbreaker for you in the original? Was it the UI clutter, specific missing wearable support, or just the lag? Tell me the one thing that made you want to delete the app.
• Where should we communicate? I’d rather not have fragmented discussions. Does a Discord server work for you, or should we keep everything on GitHub Issues?

I’m moving fast on this. Let’s make something that actually works.