That’s a harsh headline but it is unfortunately deserved. We should indeed hold Mozilla to a higher standard.
Sunday, December 17th, 2017
Friday, December 15th, 2017
I’m giving a workshop in Hong Kong on February 21st. If you’re in the area, I’d love to see you there. If you know anyone in Hong Kong, please spread the word.
This workshop will teach you how to think in a progressive way. Together we’ll peel back the layers of the web and build upwards, creating experiences that work for everyone. From URL design to Progressive Web Apps, this journey will cover each stage of technological advancement.
A rather handsome looking free serif typeface based on Gargantua. Spectral is available under an Open Font License.
Thursday, December 14th, 2017
In the name of holy engagement, the native experience of products like Twitter, Facebook, and Instagram are moving away from giving people the ability to curate. They do this by taking control away from you, the user. By showing what other people liked, or by showing recommendations, without any way to turn it off, they prevent people from creating a better experience for themselves.
Great advice from Una on getting buy-in and ensuring the long-term success of a design system.
This looks interesting—a new book by Dean Hume all about progressive web apps. A few chapters are available to download.
Monday, December 11th, 2017
I listen to a lot of podcast episodes. The latest episode of the User Defenders podcast (which is very different from the usual fare) is one of my favourites—the life and times of a NASA engineer working on everything from Apollo to the space shuttle.
You know how they say it doesn’t take a rocket scientist? Well, my Dad is one. On a recent vacation to Florida to celebrate his 80th birthday, he spent nearly three hours telling me his compelling story.
Sunday, December 10th, 2017
Visions, Ventures, Escape Velocities: A Collection of Space Futures – Center for Science and the Imagination
A collection of short stories and essays speculating on humanity’s future in the solar system. The digital versions are free to download.
Friday, December 8th, 2017
Collections of design principles that you can contribute to.
The aim of the site is to help us analyse what good Design Principles are. How Design Principles are created and measured. How they develop.
This 1993 article by Mark Weiser is relevant to our world today.
Take intelligent agents. The idea, as near as I can tell, is that the ideal computer should be like a human being, only more obedient. Anything so insidiously appealing should immediately give pause. Why should a computer be anything like a human being? Are airplanes like birds, typewriters like pens, alphabets like mouths, cars like horses? Are human interactions so free of trouble, misunderstanding, and ambiguity that they represent a desirable computer interface goal? Further, it takes a lot of time and attention to build and maintain a smoothly running team of people, even a pair of people. A computer I need to talk to, give commands to, or have a relationship with (much less be intimate with), is a computer that is too much the center of attention.
Thursday, December 7th, 2017
Relive the final trip to the moon with Geno and the crew of Apollo 17 …(real)timeshifted by 45 years.
From Scott McCloud to responsive design, Dave is pondering our assumptions about screen real estate:
As the amount of information increases, removing details reduces information density and thereby increasing comprehension.
It reminds me of Edward Tufte’s data-ink ratio.
If you’re looking for a Brighton-based junior developer, you should snap up Amber right now!
These experiments with transitioning variable font styles on hover might be silly, but I can see the potential for some beautiful interaction design.
Top of the props.
CSS properties …props …top of the. Never mind.
This CSS usage data comes from a Bing-powered scan of 2,602,016.00 pages.
Great advice on keeping your hyperlinks accessible.
When you start a redesign process for a company, it’s very easy to briefly look at all their products (apps, websites, newsletters, etc) and first of all make fun of how bad it all looks, and then design this one single design system for everything. However, once you start diving into why those decisions were made, they often reveal local knowledge that your design system doesn’t solve.
In this talk transcript, Rune Madsen enumerates the reasons for his informed scepticism towards design systems:
- The first concern, which is also the main argument of this talk, is that humans – especially designers and engineers – are obsessed with creating systems of order. This is not really driven by a demand from users, so they often tend to benefit the designer, not the user.
- My second concern relates to what I believe design systems is doing to our digital experience. We’ve always had trends in graphic design (Swiss design, Flat UI, etc), but I’m getting increasingly concerned that this broad adoption of design systems is creating a design monoculture that really narrows the idea of what digital products can be.
- My third concern is that with all this talk about design systems, there’s very little talk about the real problem in digital design, which is processes and tools. Designers love making design manuals, but any design system will completely and utterly fail if it doesn’t help people in the organization produce faster and better products.
I like this distinction between coders and developers.
The Coder is characterized by his proficiency in a narrow range of chosen skills.
By contrast the Developer’s single greatest skill is in being an applied learner.
I’m definitely not a coder. Alas, by this criterion, I’m also not a developer (because I do not pick things up fast):
Quite simply the Developer has a knack for grokking new [languages|frameworks|platforms] and becoming proficient very quickly.
I prefer Charlie’s framing. It’s not about speed, it’s about priorities:
I’m not a “developer” in that I’m obsessed with code and frameworks. I’m a “developer” as in I develop the users experience for the better.
Wednesday, December 6th, 2017
Data visualisations created for The Times, complete with code.
A great in-depth report from Alice on creating, running, and most importantly, selling an in-house design system. This makes a great companion piece to her Patterns Day talk.
Where internal teams seem to go wrong is not appreciating that the thing they’re building is still a product and so it needs to compete with other products on the market.