Vitaly’s been bitten with date-picker fever. Here’s his deep, deep, deep dive into one interface element.
I can’t remember the last time I was genuinely surprised, delighted, and intrigued by an online story like this.
Stop dilly-dallying and just get this work done, okay?
The transcript of Josh’s fantastic talk on machine learning, voice, data, APIs, and all the other tools of algorithmic design:
The design and presentation of data is just as important as the underlying algorithm. Algorithmic interfaces are a huge part of our future, and getting their design right is critical—and very, very hard to do.
Josh put together ten design principles for conceiving, designing, and managing data-driven products. I’ve added them to my collection.
- Favor accuracy over speed
- Allow for ambiguity
- Add human judgment
- Advocate sunshine
- Embrace multiple systems
- Make it easy to contribute (accurate) data
- Root out bias and bad assumptions
- Give people control over their data
- Be loyal to the user
- Take responsibility
This was my favourite talk from this year’s Interaction conference—packed full of insights, and delivered superbly.
It prompted so many thoughts, I found myself asking a question during the Q&A.
There’s a lot of great knowledge in here that can be applied to plenty of other interface elements too.
A small black mirror.
Josh gives a thorough roundup of the Interaction ‘17 event he co-chaired.
“I think I’ve distilled what this conference is all about,” Jeremy Keith quipped to me during one of the breaks. “It’s about how we’ll save the world through some nightmarish combination of virtual reality, chatbots, and self-driving cars.”
Ever been on one of those websites that doesn’t allow you to paste into the password field? Frustrating, isn’t it? (Especially if you use a password manager.)
It turns out that nobody knows how this ever started. It’s like a cargo cult without any cargo.
I really like this list of observations (Vasilis pointed it my way). I feel like it encapsulates some of what I was talking about in chapter two of Resilient Web Design. The only point I’d take issue with now is the very last one.
It reminds me of the old jQuery philosophy: find something and do stuff to it.
I wrote a while back about how I switched from using a button to using a link for progressive disclosure patterns. That looks like it was a good move—if I use a button, I’d need to use
aria-controls and, as Heydon outlines here, the screen reader support is pants.
A catalogue of objects and observations from cities around the world.
On the need for a way to mark parts of a document as “inert” while the user is interacting with modal content.
A very handy collection:
This book contains frontend coding patterns (and anti-patterns) that will assist developers in building accessible e-commerce web pages, widgets and workflows.
I like that it contains a list of anti-patterns too.
There’s also a corresponding collection of working demos.
A few common patterns—tooltips, fly-out menus, and toggles—that you can achieve with CSS.
A lovely interactive demonstration of evolution, based on the original code Richard Dawkins used for Climbing Mount Improbable.
A nice little collection of interaction patterns with built-in accessibility and no dependencies.