Our Standards

We build slowly.

A utility starts with a specific user, task, and definition of success. We release only after its complete workflow is useful, understandable on its own, and reviewed on the devices people are likely to use.

We explain our assumptions.

Calculations and recommendations are only as useful as the information behind them. Each utility should show what an output means, identify material limitations, and avoid presenting an estimate as a guarantee.

We respect your data.

Where practical, utility information stays in your browser. Local saving, portable project files, provider telemetry, and any future third-party integration must be described accurately enough for a person to make an informed choice.

We test and review.

Automated checks protect calculations, saved formats, navigation, accessibility contracts, and release gates. Human review covers the full workflow, responsive layout, understandable errors, and whether the output remains appropriate for its stated purpose.

We improve continuously.

Feedback is evaluated against documented behavior. Changes should make a tool clearer or more reliable, preserve compatible saved data when practical, and receive focused verification before release.