Roadmap — what is being worked towards, and what is not

[laurentiu021]

Direction, not dates. This is a solo project with no deadlines, so the roadmap describes what is being worked towards and roughly in what order — never what ships when.

ROADMAP.md is the document; this thread is where you can argue with it. Every roadmap item links to the issue where the real discussion happens, and the issues are the source of truth. If something on the roadmap has no issue, it is an intention rather than a plan.

Three things come up often enough to answer here.

Code signing is the largest gap, and its timing is not mine to decide. Windows warns on first launch because the binary is unsigned, and some antivirus engines flag an unknown publisher. The intended route is the SignPath Foundation programme for open-source projects, which asks for a level of public visibility — stars, external write-ups, independent references — that a project this young does not have. That is a fair bar for a certificate issued in their name, and it means the practical route to a signed build is people finding the app useful enough to say so. Until then the published SHA-256 and the GitHub build attestation are what establish that a download is genuine, and the in-app updater already refuses a signature it cannot read. The alternatives and their costs are being written up in #1675.

There will be no telemetry, no analytics, no crash-reporting service, no account and no cloud. There is no server side and there is not going to be one. Diagnostics stay on your machine and are only ever shared if you export them and send them yourself. This is not "not yet" — it is a design constraint every feature is built inside.

There will be no Microsoft Store build. The Store sandbox forbids most of what this app does: reading other processes' working sets, writing the hosts file, changing services and scheduled tasks, purging the standby list. A Store version would be a different and much smaller app wearing the same name.

The rest of the roadmap is about making the app explain itself, because the person it is built for wants their PC to run better and has no reason to know what a working set is.

What would help most: tell me which of these you actually care about, and which ones you would never use. A ranked backlog written by one person is a guess. If something you want is missing, open an issue or say so below — half-formed thoughts are fine here.