Archive: August 23rd, 2019

Stop Misusing Toggle Switches

Use a toggle switch if you are:

  1. Applying a system state, not a contextual one
  2. Presenting binary options, not opposing ones
  3. Activating a state, not performing an action

Brendan Dawes - Adobe Alternatives

Brendan describes the software he’s using to get away from Adobe’s mafia business model.

Replying to a tweet from @rem

Ooh! Colour me intrigued!

Gonna blog about it?

Replying to a tweet from @drinkerthinker

I want to go to there.

Replying to a tweet from @charlesarthur

By the way, Charles, the one comfort I can take about AMP is that every passing day brings us closer to its 1,459 day probability point.

Replying to a tweet from @rem

Here’s what I just got on …but no fireworks.

Here’s what I just got on …but no fireworks.

Replying to a tweet from @rem

One more point and there’ll be fireworks:

Replying to a tweet from @adactio

Related: here’s what I’ve been reading, documented on my website:

Replying to a tweet from @adactio

So, just to be clear, while you might be capable of the mental gymnastics required to think “Well, leaving aside the unfairness of the SEO situation with AMP…”, I cannot do that.

I wish AMP would compete on its own merits.

Do it.


Replying to a tweet from @pbakaus

Me too! I would love to get behind AMP—a declarative framework where configuration happens in HTML rather than JavaScript: great!

But I cannot in good conscience support it while it is being unfairly prioritised and propped up in search.

Replying to a tweet from @pbakaus

It is not orthongonal as long as AMP is being privileged in search. This isn’t something you can just handwave away. The unfairness of it actively harms AMP-as-framework.

Replying to a tweet from @colly

Also YES

Queen Mary 2 | Flickr

Jessica’s photos from our transatlantic crossing. Swanky!

Sunset from the Commodore Club

Intentional and Emergent Design Systems | Jordan Moore

This is a really interesting distinction:

An intentional design system. The flavour and framework may vary, but the approach generally consists of: design system first → design/build solutions.

An emergent design system. This approach is much closer to the user needs end of the scale by beginning with creative solutions before deriving patterns and systems (i.e the system emerges from real, coded scenarios).

It’s certainly true that intentional design systems will invariably bake in a number of (unproven?) assumptions.

Replying to a tweet from @tobie

I have no problems with AMP, the open source format (accessibility issues notwithstanding).

I have no problems with AMP’s governance model.

I have serious problems with AMP’s privileged position in Google Search. It’s an abuse of power.

Replying to a tweet from @pbakaus

Agreed! Maintaining one site is nicer than two.

And yet publishers with already-fast sites (like The Guardian) are compelled to make AMP versions for the search benefits.

That’s not a side point—it is THE point!

Replying to a tweet from @voxpelli

I like it!

Taking shortcuts ・ Robin Rendle

How Robin really feels about Google AMP:

Here’s my hot take on this: fuck the algorithm, fuck the impressions, and fuck the king. I would rather trade those benefits and burn my website to the ground than be under the boot and heel and of some giant, uncaring corporation.

Is client side A/B testing always a bad idea in your experience? · Issue #53 · csswizardry/ama

Harry enumerates the reasons why client-side A/B testing is terrible:

  • It typically blocks rendering.
  • Providers are almost always off-site.
  • It happens on every page load.
  • No user-benefitting reuse.
  • They likely skip any governance process.

While your engineers are subject to linting, code-reviews, tests, auditors, and more, your marketing team have free rein of the front-end.

Note that the problem here is not A/B testing per se, it’s client-side A/B testing. For some reason, we seem to have collectively decided that A/B testing—like analytics—is something we should offload to the JavaScript parser in the user’s browser.

4 Rules for Intuitive UX – Learn UI Design

  1. Obey the Law of Locality
  2. ABD: Anything But Dropdowns
  3. Pass the Squint Test
  4. Teach by example

Replying to a tweet from @scottjehl

Yup! See you soon!

Replying to a tweet from @gregolls

The Arrogance of the Anthropocene - The Atlantic

If, in the final 7,000 years of their reign, dinosaurs became hyperintelligent, built a civilization, started asteroid mining, and did so for centuries before forgetting to carry the one on an orbital calculation, thereby sending that famous valedictory six-mile space rock hurtling senselessly toward the Earth themselves—it would be virtually impossible to tell.

A nice steaming cup of perspective.

If there were a nuclear holocaust in the Triassic, among warring prosauropods, we wouldn’t know about it.

Replying to a tweet from @pbakaus

…but if you use any framework other than AMP, you don’t get any of the Google Search benefits that are only bestowed on sites “choosing” to use AMP.

Hardly seems fair.

Replying to a tweet from @cramforce


Far from questioning AMP’s right to exist, I want it to exist and compete on a level playing field—without being propped up by an unfair advantage in search results.

Classic fascism, that.

Walking on the beach at sunset.

Walking on the beach at sunset.