Journal

Why we build calm, honest software

Open almost any app on your phone and watch what it does in the first ten seconds. A streak counter flashes red because you skipped a day. A notification tells you someone is "waiting" on you, except no one is. A price you didn't agree to renews automatically, buried under three menus you'd never think to check. A "free" trial asks for your card up front, betting you'll forget to cancel. None of this is an accident. It's a design discipline, taught in courses and written up in playbooks, and its explicit goal is to make you do things you wouldn't choose to do if you were thinking clearly.

I don't think that's a fringe problem anymore. It's the default. Most consumer software today is built by teams whose bonus depends on engagement metrics going up, and the fastest way to move an engagement metric is to borrow against a user's attention, guilt, or fear of missing out. It works, in the narrow sense that the number goes up. It also means people end up managing their relationship with their phone instead of their life.

The bet I'm making instead

Everlight Digital is a one-person studio, which means I don't have a growth team pushing me toward these tactics, and I don't answer to a board that wants quarter-over-quarter engagement. I get to just decide not to do it. So that's the bet: build software that respects the fact that your attention is yours, not mine to extract.

Concretely, that means a few rules I hold myself to across everything I ship:

• No manufactured urgency. If a feature needs a countdown timer or a fake "3 people are viewing this" banner to get used, it's not a feature worth having.
• No guilt mechanics. Streaks that punish you for living your life, red badges that exist purely to nag, "you haven't opened this in 3 days" push notifications — I don't build them. If someone stops using an app of mine, that's information for me, not a problem to solve by shaming them back in.
• Fair, visible pricing. One price, clearly stated, no dark-pattern cancellation flows. If a subscription isn't worth what it costs, the answer is to make the product better, not to make canceling harder.
• Data stays boring. I don't sell it, I don't build shadow profiles, and I try to collect as little as the feature actually needs.

What this looks like across the apps

This isn't just a mission-statement page — it shapes actual product decisions. Pilgrim, a Bible reading app, deliberately has no streak counter and no shame if you miss a day; showing up occasionally with an open heart is still showing up. Shepherd, which helps pastors track pastoral care for their congregation, charges one flat price per tier instead of nickel-and-diming per-member add-ons, because a pastor shouldn't have to do math to decide whether checking on someone is affordable. Regen, a recovery and training dashboard, shows you your real recovery numbers instead of gamifying them into a score designed to keep you opening the app. Olive, a family organizer still in the works, keeps the household's week in one calm place without turning chores into a badge-and-streak game.

None of these are radical ideas. They're just what software looks like when the person building it isn't optimizing for a metric that fights against your actual interests.

Why this is sustainable, not just idealistic

I'll admit the calm-software pitch can sound like a nice sentiment that doesn't survive contact with a real business. I don't think that's true, and I think the reason is simple: manipulative software creates a lot of quiet resentment. People keep paying because canceling is a hassle, or because a streak has psychological weight, but they don't feel good about it, and eventually they leave anyway — just later, and angrier. A tool that respects you is one you actually want to keep using, and that's a better foundation for a small, long-term studio than any growth hack.

I'm not trying to convince you this is the only way to build software, or that every dark pattern is malicious — some of it is just companies chasing quarterly numbers under real pressure. I'm just telling you what I've decided to build instead, and why. If that's the kind of software you want to use, that's what you'll find across everything below.