Akhouri Systems has reached 513 downloads.
My next milestone is 600.
That means I need 87 more.
But after building ATLOCK for months, I’ve realized something:
A download by itself doesn’t tell me much.
Someone can download an application, open it once, and never touch it again.
What I actually want is feedback.
So I’m changing the goal.
ATLOCK v4 Community Testing Week
Instead of asking people to simply download ATLOCK, I’m asking Windows users to try to break my assumptions about the product.
ATLOCK currently includes:
🔒 NTFS-based File Protection
🔐 Encrypted Password Vault
📸 Intruder Ops
🖥️ Desktop Lockdown
📋 Local Security Logs
I don’t want another list of compliments.
I want someone to say:
“This workflow makes no sense.”
Or:
“Why doesn’t it do this?”
Or:
“I’d completely redesign this part.”
That’s useful.
Why?
Because when you’re an independent developer, you spend so much time inside your own project that you start seeing it the way you designed it, rather than the way a new user experiences it.
That’s dangerous for software.
Especially for security software.
A security application can have technically interesting features and still fail if the user doesn’t understand what it’s doing.
So I’m opening the project to community testing.
The challenge
Current: 513 downloads
Target: 600
Remaining: 87
But I’m measuring more than downloads this time.
I want to know:
What confused you?
What felt unnecessary?
What felt genuinely useful?
What would make you trust the application more?
What feature would you add?
If you’re a Windows user, I’d genuinely appreciate 10 minutes of your time.
🔗 ATLOCK v4:
https://github.com/Akhouri-Anmol-Kumar/ATLOCK
And if you find something wrong with it, please tell me.
I’d rather fix a real problem than collect another meaningless compliment.
One question for developers:
What’s the most valuable criticism you’ve ever received about something you built?
I’m especially interested in the answers from people who have shipped their own software.
답글 남기기