Thinking out loud.

Why we started KindSoft.

The short answer: because the software we needed didn't exist, and the people building it weren't the people using it.

The longer answer involves a diagnosis, a career in healthcare IT, and the realization that understanding a problem from the inside is a fundamentally different thing than understanding it from the outside. When you've sat in the chair, used the tool at 2 AM, and felt the friction of software that was designed in a conference room — you can't unsee it. So you build something better.

KindSoft is the company behind that impulse. Not a single product. A way of thinking about what software owes the people who use it.

Why we don't have servers.

Most software companies start with a database. Postgres, MongoDB, DynamoDB — pick your flavor. User data goes in. Revenue model figures out how to keep it there. Privacy policy explains what you'll do with it. Security team tries to make sure nobody else gets at it.

We skipped all of that.

KindSoft apps use Apple's CloudKit with the user's own private database. That means your data lives in your iCloud account, encrypted by Apple, accessible only by your Apple Account credentials. We don't administer the database. We can't query it. We can't export it. We can't accidentally leak it in a breach, because we never had it in the first place.

This isn't a limitation — it's the entire architecture. The safest way to handle sensitive data is to never handle it. Every decision flows from that principle.

Designing for the worst moment of someone's day.

Most apps are designed for the demo. The screenshot. The "look how clean this is" moment that gets likes on Dribbble. The user in the designer's head is calm, attentive, well-rested, and sitting at a desk with good lighting.

Our users aren't that person.

They're exhausted. They're in the middle of something. They're using the app because they have to, not because they want to. The moment they open our software is often the worst part of their day — and if the app adds even one unnecessary tap, one confusing label, one "where did that button go?" moment, we've failed.

This is what "kind software" means in practice. It's not about being nice. It's about being considerate of the human on the other side of the screen — their energy, their time, their cognitive load. Every design decision at KindSoft starts with the question: "What if the person using this is at their absolute limit right now?"

If the design works for that person, it works for everyone.