Over the years, I have developed a set of principles that guide every decision I make when building software. These are not theoretical ideals but practical commitments. From the first line of code to every update after, I return to these principles to ensure I am creating tools that truly serve their users.

Here are the principles:

Uncompromising Privacy

Privacy comes before everything else. Users should never have to trade privacy for convenience. Every feature I build respects this. Data stays on the user’s device. Always. I do not collect what I do not need, and I do not need much. If a feature requires sending data to a server, I make it clear in the privacy policy exactly what is sent and why. My software will never use analytics, tracking, or advertising services. Privacy is not a premium add-on or an afterthought. It is the foundation of all software I build.

Complete Transparency

I am clear about what my software does, how it works, and what data it uses. No vague privacy policies written to confuse. When something changes, I explain why in release notes or on the blog. When something breaks, I own it. I also list the open-source software I use in the acknowledgments page, so you know what is inside my software.

Built to Complete

I build software to help people get things done, not to keep them engaged. Every second saved is a second returned to the user. This means my software is designed to be fast, with minimal steps and no unnecessary things. Software should get out of the way once it has done its job. I do not measure success by how long people use my software. I measure it by how quickly they can accomplish what they need and move on with their lives.

Moving Toward Open Source

I am committed to open sourcing the building blocks of my software. This means libraries, tools, and components that others can use in their own projects. Not everything can or will be open immediately. Some pieces need time to mature. Some have dependencies that complicate things. But my goal is clear: over time, more of the components I build will be open. Open source builds trust. It allows others to learn from my work and build upon it. It holds me accountable to higher standards.

Open Dialogue

I love hearing from people who actually use my software rather than guessing patterns from analytics dashboards. Whether through email or support requests, I listen to what people actually experience. Real feedback tells me what works, what frustrates, and what needs to change. I invite you to help make the software better.

Yours truly,

kevin AT hermawan DOT ai