Chrome bias, out in the wild!

About two weeks ago I read this fairly old article (published in 2018) about the trending bias towards Chrome optimised web experiences in the design/development ecosystem.

Kind of fascinating that today, whilst looking up the latest alternatives to Hotjar for my non-profit clients, up pops little alert when signing in to Userzoom:

A screenshot of a login page for UzerZoom GO. The key part of the screenshot is that overlain on top of the log in fields (but offset towards the left so the fields for email and password can be clearly seen) is an error notice that reads: 'An error has been detected. We only support Google Chrome browsers. If you experience problems in your browser, please use Chrome.'

Building Nonlinear Narratives for the Web

A very inspiring and helpful article for someone also working on a similar project:

The web operates in ways that can conflict with our traditional view of what a “story”—with a set start, middle, and end—is. Content is chunked, spread across various channels, devices, and formats. How do we define story lines, characters, interactions, and the role of the audience, given this information sprawl?

Building Nonlinear Narratives for the Web