A sweeping majority of web-native teams I've met do cross-browser cross-device testing and intentionally make sure their team has multiple browsers/devices represented by engineers during development.
Serious shops have literal walls of devices for automated testing across different browsers and OS stacks, with real-time Quality of Experience metrics streaming back from customer devices - tagged with environment metadata - to detect regressions to the experience on every release.
I find it hard to believe that one of the largest web-native giants in our industry didn't follow those practices as an oversight. I hold engineers at Google in higher regard than that.
Comments
A sweeping majority of web-native teams I've met do cross-browser cross-device testing and intentionally make sure their team has multiple browsers/devices represented by engineers during development.
Serious shops have literal walls of devices for automated testing across different browsers and OS stacks, with real-time Quality of Experience metrics streaming back from customer devices - tagged with environment metadata - to detect regressions to the experience on every release.
I find it hard to believe that one of the largest web-native giants in our industry didn't follow those practices as an oversight. I hold engineers at Google in higher regard than that.