I didn’t plan to build an app catalog.
I just wanted to fix one annoying problem: my C: drive kept filling up at the worst possible time (usually during releases, obviously).
So I built a cleanup tool for myself.
Then I built another tool.
Then another.
Now WPZ Studio has become a small universe of desktop apps.
The accidental roadmap
The pattern was simple:
- Hit a repetitive pain point
- Build a focused tool
- Use it daily
- Improve it when it annoys me again
Very glamorous. Very “indie dev meets chaos management.” 😄
What I ended up building
Instead of one app, it turned into a full lineup:
- Productivity tools (clipboard, file utilities, zip/PDF/Excel helpers)
- Utility + diagnostics tools (network checks, log analysis, cleanup)
- Developer-focused tools (event log analysis, Terraform workflow support)
- Plus education apps and even a desktop pet, because not every app has to be serious
If your computer has ever made you whisper “why are you like this,” I probably built something for that mood.
The website side
The repo is a GitHub Pages site that works as a live app catalog with:
- category filters
- keyword search
- sorting
- multilingual content
So yes, I built tools to save time, then built a site to organize the tools I built to save time.
The recursion is complete.
Why I keep doing this
I like shipping software that solves specific, boring, real problems:
- “What changed in these two Excel files?”
- “Why is this server acting weird?”
- “How is disk space gone again?”
- “Can this repetitive task just disappear?”
For me, good desktop software should be boring in the best way: reliable, fast to learn, and always there when needed.
If you want to explore WPZ Studio
Question for fellow builders: what’s one tiny-but-annoying workflow you wish someone would turn into a desktop app next?