Negativity bias

When I wrote about my hopes and fears for the View Transitions API, a few people latched on to this sentiment:

If the View Transitions API only works for single page apps, it could be the single worst thing to happen to the web in years.

But I also wrote:

If the View Transitions API works across page navigations, it could be the single best thing to happen to the web in years.

I think it’s worth focusing on that.

Part of the problem is that I gave my hopes and fears an equal airing. But they’re not equally likely.

Take the possibility that the View Transitions API only ships for single page apps, but never ships for regular page transitions. The consequences of that would be big—the API would act as an incentive to build single page apps. But the likelihood of that happening is small. In fact, according to Jake, there’s already an implemention for page transitions in the works at Chrome.

Now what if the View Transitions API ships for pages? The consequences would be equally big—the API would act as an incentive to ditch single page apps and build in a more performant, resilient way. Best of all, the chances of that happening are very large indeed (pretty much a certainty now, given Jake’s update).

So I made a comparison between both of the consequences, which are equally large, but I didn’t make a corresponding comparison of the likelihoods, which are not equally large. Mea culpa!

I should’ve made it clearer that, although the consequences would be really bad if the View Transitions API only supports single page apps, the actual likelihood of that is pretty slim.

That’s probably my negativity bias showing through. (The reason I have a negativity bias is because I am a human. Like, have you ever noticed that if you get feedback on something and 98% of it is positive, you inevitably fixate on the 2%?)

Anyway, the real takeaway here is that if the View Transitions API ships for pages, then the consequences will be really, really good! It would be another nail in the coffin for monolithic JavaScript frameworks slowing down the web. And best of all, the likelihood of this happening is very high!

So let me amend my closing sentences from my previous post:

If the View Transitions API only works for single page apps—which is very unlikely—it could be the single worst thing to happen to the web in years.

If the View Transitions API works across page navigations—which is very, very likely—it could be the single best thing to happen to the web in years.

The glass is half full and it’s only going to get fuller. Time to start planning for a turbo-charged web now.

If you’ve got a website with full page navigations, start thinking about how you’ll be able to apply the View Transitions API as a progressive enhancement to improve the user experience.

If you’ve got a single page app, start thinking about how to ditch a whole bunch of uneccessary dependencies to make a more lightweight foundation of HTML instead of JavaScript, and still get all those slick transitions you get in a single page app!

Have you published a response to this? :

Responses

Baldur Bjarnason

“Adactio: Journal—Negativity bias” View Transition API shipping for both SPAs and MPAs would be a breakthrough for web dev. You need both because it, combined with the Navigation API could simplify SPAs greatly. adactio.com/journal/19578

1 Like

# Liked by Baldur Bjarnason on Saturday, November 5th, 2022 at 6:37pm

Related posts

Image previews with the FileReader API

Adding `alt` text to uploaded images.

Browser defaults

What would the repercussions be if browsers were to tweak some of their default behaviours?

Vertical limit

The headache of an inconsistent viewport.

Someday

Changing defaults in browsers …someday.

Bugblogging

Also, tipblogging.

Related links

a view source web

As a self-initiated learner, being able to view source brought to mind the experience of a slow walk through someone else’s map.

This ability to “observe” software makes HTML special to work with.

Tagged with

Modern CSS in Real Life - Chris Coyier

This is a terrrific presentation by Chris, going through some practical implementations of modern CSS: logical properties, viewport units, grid, subgrid, container queries, cascade layers, new colour spaces, and view transitions.

Tagged with

Tagged with

Jeremy Keith on your content, failing well, and the Indie Web Movement - YouTube

I had a chat with some people from Name.com while I was in Denver for An Event Apart. Here’s a few minutes of me rambling on about web development and the indie web.

Tagged with

Release Notes for Safari Technology Preview 46 | WebKit

Well, that escalated quickly! Service workers are now available in Safari’s Technology Preview, which means it won’t be long before it lands in Safari proper.

Also: service workers also just landed in the insider release of Edge.

Everything offline’s coming up Milhouse!

Tagged with

Previously on this day

3 years ago I wrote Memories of Ajax

A Netflix series today reminds me of something from 15 years ago.

14 years ago I wrote Drafty

Publish or be damned.

17 years ago I wrote Berlin, day 1

Touristische sachen.

18 years ago I wrote Geekend in Ironbridge

Five go to Shropshire… well, a lot more than five, actually.

21 years ago I wrote Less blog, more rock

It looks like I’m going to have to miss the Brighton Bloggers meetup tomorrow night in the Wi-Fi enabled Black Lion pub. There’s a Salter Cane gig happening down at the Freebutt and I have yet to master the art of bilocation.

22 years ago I wrote v-2

Adam Greenfield’s website just got even better. It now uses a lean mean combo of XHTML and CSS.

22 years ago I wrote Lost Weekend

It’s been a wild weekend of music.

23 years ago I wrote My new scarf

Despite the warmest October since records began, I’m not going to let the nice weather fool me.

23 years ago I wrote The world outside my window

It’s another lovely day in Brighton.