That's exciting.
But there's something I've realized while building it:
A download doesn't tell you whether your software is actually good.
Someone can download an application, open it once, and never touch it again.
So I'm changing what I want from the next 100 downloads.
I don't just want people to download ATLOCK.
I want people to test it.
What should you test?
ATLOCK v4 currently includes several local Windows security functions:
🔒 File Guard
🔐 Password Vault
📸 Intruder Ops
🔔 Security Notifications
🖥️ Desktop Lockdown
But don't just look at the feature list.
Actually use them.
Try the workflows.
Look through the settings.
See whether something is confusing.
See whether something feels unnecessary.
And if something breaks, tell me.
Why I'm asking
I'm building ATLOCK independently under Akhouri Systems.
I don't have a large QA department.
I don't have a team of testers sitting around checking every workflow.
The people who actually download and use the application can provide something that automated testing can't:
real-world feedback.
And that's much more valuable to me than someone simply saying:
"Nice project."
🔒 Try ATLOCK v4
GitHub:
https://github.com/Akhouri-Anmol-Kumar/ATLOCK
If you use Windows, give it a try.
And if you do download it, I have one question:
What was the first thing you tested?
That's the feedback I'm looking for.
532 downloads so far.
Now let's see how many people are willing to actually put it through its paces.
ATLOCK
"We Build What Others Forgot To Fix"
Top comments (2)
"A download doesn't tell you whether your software is actually good" is the right shift to make, and it's a rarer thing to admit publicly than it sounds, most solo devs treat download count as the finished metric because it's the easiest one to point at, even though everyone quietly knows it doesn't measure usage.
The specific ask ("what was the first thing you tested") is smarter than a generic feedback request too, it gives people a low-effort way to respond with something real instead of defaulting to a compliment, and it'll probably tell you which feature people trust enough to try first, which is its own useful signal before anyone reports a bug.
Exactly! 542 downloads is a nice milestone, but actual usage is the metric I care about now.
And you're right about the “first thing you tested” question — it's a much easier way to get genuine feedback than asking for a generic review. I'm curious to see which feature people naturally test first. 👊