MDN-Browser-Compatibility-Report-2020

Strongly Dissatisfied

Browser Comgatibilit)l

Are web devs 4) Based on your experience developing for If devs already claim to be more or less the web, how satisfied or dissatisfied are satisfied with you with browser compatibility? compat than overall? 5-point satisfaction scale. Hypothesis: much less satisfied. satisfied that's surprising, ask in interviews if there's something more frustrating.

Repeat this compat satisfaction question over time to see if our efforts are working. Identify the top compat pain points to focus on in the interviews. Nothing if the hypothesis is confirmed. If falsified, focus on the surprising aspect in interviews. If "knowing" is at the top we prioritize compat data and its use in products. If prefixes are at the top we prioritize unprefixing in all engines.

What is top of 5) Overall, what is your top pain point with mind with browser compatibility? compat? [open text field] Where are the 6) What are the biggest pain points for you biggest pain when it comes to browser compatibility? points at a Select up to 3. high level? 0 Lack of browser support for a given Hypothesis is feature the first two. 0 Differences between browsers for a given feature 0 Knowing what browsers support a given feature 0 Managing polyfills 0 Managing workarounds for browser bugs 0 Getting equivalent performance 0 Dealing with prefixes 0 Other: ... Which specific 7) What feature areas cause the most features that issues with browser compatibility? Select can be up to 3. improved by o Accessibility specific teams 0 Animations are the 0 Device access (camera, sensors,

Focus on the most selected areas in follow-up interviews.

Expected top area is layout.

biggest

etc.)

DOM APls (modifying elements,

source of

0

frustration?

editing, selection, etc.)

Fonts

0

0 Forms (autocomplete, styling, etc.)

Made with FlippingBook - professional solution for displaying marketing and sales documents online