davidbgk
/
larlet-fr-david-cache
Observar 1
Favorito 0
Fork 0
Código Versões 0 Atividade
A place to cache linked articles (think custom and personal wayback machine)
Você não pode selecionar mais de 25 tópicos Os tópicos devem começar com uma letra ou um número, podem incluir traços ('-') e podem ter até 35 caracteres.
224 Commits
1 Branch
Tag: f8f4c58548
Branches Tags
${ item.name }
Criar branch ${ searchTerm }
de f8f4c58548
${ noResults }
larlet-fr-david-cache/cache/ab325197a8e81f929de1b10477c.../index.md

index.md 3.5KB
Original Anotar Histórico

title: Calm Technology url: https://calmtech.com/ hash_url: ab325197a8

Our world is made of information that competes for our attention.
What is necessary? What is not?

When we design products, we aim to choose the best position for user interface components, placing the most important ones in the most accessible places on the screen.

Equally important is the design of communication. How many are notifications are necessary? How and when should they be displayed? To answer this, we can be inspired by the principles of calm technology.1

Principles of Calm Technology

  1. Technology should require the smallest possible amount of attention

    1. Technology can communicate, but doesn’t need to speak.
    2. Create ambient awareness through different senses.

    3. Communicate information without taking the wearer out of their environment or task.

  2. Technology should inform and create calm

    1. A person’s primary task should not be computing, but being human.
    2. Give people what they need to solve their problem, and nothing more.

  3. Technology should make use of the periphery

    1. A calm technology will move easily from the periphery of our attention, to the center, and back.
    2. The periphery is informing without overburdening.

  4. Technology should amplify the best of technology and the best of humanity

    1. Design for people first.
    2. Machines shouldn’t act like humans.
    3. Humans shouldn’t act like machines.
    4. Amplify the best part of each.

  5. Technology can communicate, but doesn’t need to speak

    1. Does your product need to rely on voice, or can it use a different communication method?
    2. Consider how your technology communicates status.

  6. Technology should work even when it fails

    1. Think about what happens if your technology fails.
    2. Does it default to a usable state or does it break down completely?

  7. The right amount of technology is the minimum needed to solve the problem

    1. What is the minimum amount of technology needed to solve the problem?
    2. Slim the feature set down so that the product does what it needs to do and no more.

  8. Technology should respect social norms

    1. Technology takes time to introduce to humanity.
    2. What social norms exist that your technology might violate or cause stress on?
    3. Slowly introduce features so that people have time to get accustomed to the product.