Enter UA-CH lies

Just like predicted, we’re back to square 1 with UA-CH vs. User-Agent.


Unfortunately, I can’t document the following claim, but I’m pretty sure that this is the case:

The reason for minority browser being locked out and/or getting a degraded experience, is client side (JavaScript) user-agent (or now UA-CH)- sniffing, performed by junior webdevs.

Vivaldi’s experience is proof enough that UA-CH sniffing is bad practice. The UA-CH initiative only made the problem worse by giving more powerful tools and lowering the efforts to make use of them (the UA-CH js api totally ungated! 🤦‍♂️)

Now, situation is worse than before UA-CH. With only the user-agent we had only one lie which could be well managed by proper device detection. Now we have two lies which may tell separate stories.

Comments are closed.