Useful before impressive
Start with a real task. Make the main path obvious. Add complexity only when it earns its place.
Our working standards for everything we put our name on.
Start with a real task. Make the main path obvious. Add complexity only when it earns its place.
No manufactured urgency, misleading buttons, or surprise commitments. Explain exactly what is being offered.
Keep tools responsive and resource use proportionate. The website should load quickly and work without unnecessary scripts.
Prefer local processing where practical. State what leaves the device, which services are involved, and what control the user has.
Use a one-time price when it suits the product. Subscriptions should provide ongoing value. State taxes, renewals, and upgrade terms clearly.
Readable type, visible focus, keyboard access, reduced motion, and flexible layouts belong in the design from the beginning.
Use a consistent product catalogue and reusable patterns, while letting each app explain its own purpose.
Publish real capabilities and real limitations. Distinguish planned work from released features. Give customers a clear support route.
If an app falls short of these principles, we want to hear about it.