All Posts, page 23

Marco Arment:

Even with almost no complications, the basic essence of the Infograph dial has poor time legibility.

Miles Klee, for MEL Magazine:

“Every homeless person has like three scooters now,” Michael Ghadieh, owner of an electric bike store in San Francisco, told CNET. “They take the brains out, the logos off and they literally hotwire it.”

Ben Frain gives some very useful and pragmatic advice on how to build web front-end prototypes.

Producing something of high fidelity, perfectly matching any flat designs, runs counter to the notion of creating something quickly. The challenge for the prototyper is therefore how to cut corners that don’t impact the fidelity of the prototype.

Jeremy Keith adds:

In my experience, it’s vital that the prototype does not morph into the final product …no matter how tempting it sometimes seems.

Prototypes are made to be discarded (having validated or invalidated an idea). Making a prototype and making something for production require very different mindsets: with prototyping it’s all about speed of creation; with production work, it’s all about quality of execution.

Max Böck:

Text-only sites like these are usually treated as a MVP of sorts. A slimmed-down version of the real site, specifically for emergencies.

I’d argue though that in some aspects, they are actually better than the original.

This is the web as it was originally designed. Pure information, with zero overhead. Beautiful in a way.

Jeremy Keith:

I really like this design pattern. Cover 80% of the use cases with a declarative solution in HTML, but also provide an imperative alternative in JavaScript that gives more power. HTML5 has plenty of examples of this pattern. But I feel like the history of web standards has a few missed opportunities too.

In recent years there’s been a push to expose low-level browser features to developers. They’re inevitably exposed as JavaScript APIs. In most cases, that makes total sense. I can’t really imagine a declarative way of accessing the fetch or cache APIs, for example. But I think we should be careful that it doesn’t become the only way of exposing new browser features. I think that, wherever possible, the design pattern of exposing new features declaratively and imperatively offers the best of the both worlds—ease of use for the simple use cases, and power for the more complex use cases.

Rachel Andrew:

There is frequently talk about how developers whose main area of expertise is CSS feel that their skills are underrated. I do not think we help our cause by talking about CSS as this whacky, quirky language. CSS is unlike anything else, because it exists to serve an environment that is unlike anything else. However we can start to understand it as a designed language, with much consistency. It has codified rules and we can develop ways to explain and teach it, just as we can teach our teams to use Bootstrap, or the latest JavaScript framework.

A look at the 12 principles of animation developed by Disney to give life to an image.

Explainers about Disney’s animation techniques have been done to death, but Kristian’s stellar editing and compositing make this one worth watching. He uses some great examples that I hadn’t seen before.