✳flâneur — a map of the web's best reading

Responsive interfaces

devouringdetails.com · 866 words · saved by 1 readers

I like to think of design as an asynchronous conversation between you and the human on the other end using your interface. Only you aren't conversing directly with words, but through your design decisions they have to interact with. But if they were sitting right across from you, narrating a story, you would likely give them tactful feedback by either nodding, asking follow up questions, or laughing. In various ways this lets them know that you understood them and are present. Similarly, nearly all interactions you perform on a software system must respond with some form of feedback. This "input-response" loop is why the text caret starts blinking when you stop typing—it communicates that the system is still responsive to your next input, and did not suddenly freeze. Loading indicators communicate that the system understood you and is currently thinking of a response. We can say that an interaction is jarring when the response on the screen was not appropriate for the input or dismisse

Devouring Details Have you ever noticed that some animation sequences can be improved with just a touch of delay? Or that some interactions just feel better without any motion at all? Devouring Details is an interactive reference manual for interaction-curious designers, containing 23 chapters with 23 downloadable React components. All footage is recorded of React components Platform Before working on this I thought to myself: “how have I learned myself?” By trying to build an idea and realising it sucks in practice. With enough iterations and sometimes by accident I’ll get to a place where it

Explore this link on the map →

related reading