Home
Categories
EXPLORE
True Crime
Comedy
Society & Culture
Business
Sports
Technology
Health & Fitness
About Us
Contact Us
Copyright
© 2024 PodJoint
Podjoint Logo
US
00:00 / 00:00
Sign in

or

Don't have an account?
Sign up
Forgot password
https://is1-ssl.mzstatic.com/image/thumb/Podcasts116/v4/66/bb/9b/66bb9bc6-44b9-f8b0-4112-fd992796d706/mza_7832869939483414117.jpg/600x600bb.jpg
Hidden By Design
Hidden By Design
46 episodes
6 days ago
We believe that the best and most pleasurable design, is the design that you dont see, the design that is hidden, and works without you noticing.
Show more...
Design
Arts
RSS
All content for Hidden By Design is the property of Hidden By Design and is served directly from their servers with no modification, redirects, or rehosting. The podcast is not affiliated with or endorsed by Podjoint in any way.
We believe that the best and most pleasurable design, is the design that you dont see, the design that is hidden, and works without you noticing.
Show more...
Design
Arts
https://d3t3ozftmdmh3i.cloudfront.net/production/podcast_uploaded_nologo/36432681/36432681-1678173730952-19be4d7a4a7a.jpg
Postels Law
Hidden By Design
28 minutes 8 seconds
1 year ago
Postels Law

Postels law, also known as the "Robustness principle" originally comes from the development and ideas of how the internet should be designed. The TCP (Transmission Control Protocol) was designed with the following sentence as a central point "be conservative in what you do, be liberal in what you accept from others".

How is this related to design you might ask? Well, really simple, because this can be directly applied to how you should think about design. Think about an input field and how it should be conservative in what it shows.

There should be a field, there should be a small explanation on what is expected in the field (email), and an example in the field helping the user (example@email.com) This should make sure that the user have a clear understanding of what is expected, and the context of the situation. However, once the user starts using it, the input field should accept that the user might make some mistakes. This could be the situation where the user is copy/pasting the email from another loaction, and there is a space at the end of the email. There is no emails that end with a space, (or starts with a space) but instead of just throwing an error in the direction of the user, we should silently understand that the space is not a valid charater and remove it, and handle the situation without bothering the user.

And this does not only apply to UI design, which is often used as an example on where to use this, but also when you are working with UX.

Here we are back to the basics that we talked about in the episode "What is Design" where we talked about the importance of understanding that the actor (our user) makes decisions in an environment (the context) and that we have to design our solution (object) in a way that caters for that. In the end, we know what we want the user to do, but we accept that there is a high chance that they will do something different (and something that could be considered an error) and we have to help them recover from these actions.

Give this episode a listen, its good !

You will learn

  • Who Jon Postel is
  • What Postels law is
  • How to apply Postels law

References

Die Antwoord

Nudging

What is design

Hidden By Design
We believe that the best and most pleasurable design, is the design that you dont see, the design that is hidden, and works without you noticing.