Postel's Law
Be liberal in what you accept and conservative in what you send: accept messy user input gracefully, and respond in clear, consistent ways.
Key takeaways
- Accept many input formats (dates, phone numbers, spaces) and normalize them yourself.
- Don't reject input for formatting the system could fix.
- Keep output — messages, data, layouts — predictable and consistent.
Origin
Formulated by internet pioneer Jon Postel as the robustness principle in the early TCP specification (RFC 761, 1980), and since adopted as a general design principle.
How to apply it
- Accept common variations in input formats and normalise them automatically.
- Correct or suggest fixes for typos instead of rejecting input.
- Validate only what really needs validating, and explain errors clearly.
- Keep your outputs consistent and predictable.
- Design for different devices, input methods, screen sizes and assistive technologies.
How Science of Apps uses this law
5 checks in every investigation rely on Postel's Law, for example: “Is search visible where users expect it and does it tolerate typos and synonyms?”
Get your product investigated