Focused software
A product should solve a specific problem well, without becoming a container for unrelated features.
Principles
Restraint is a product decision.
A short set of working principles guides what we build, what we leave out, and how clearly we communicate both.
Transparent behavior
People should be able to understand what software changes, what it depends on, and where its limits are.
No dark patterns
Choices should be clear. Interfaces should not pressure people into accounts, subscriptions, or permissions.
Local-first where practical
When a task can be handled responsibly on the device, unnecessary cloud dependencies should not stand in the way.
Controlled, reversible changes
System-level software should make deliberate changes and provide a reliable path back.
Honest capability claims
Useful software does not need inflated promises. Boundaries and tradeoffs belong in the product story.