Browsers The primary audience for this report is browser vendors. Unlike with the findings for features , where we have sometimes dug deep to explain the results, for specific browsers we have sought to avoid interpretation or explanation, and to instead relay the survey results as directly as possible. This is to allow each browser vendor, who are the premiere experts on their own browser, to do their own analysis and take what value they can from this report. Quotes from the interviews are not repeated here, as many examples have already appeared in the findings for features , and all of them can be found in the interview transcripts . Chrome In browsers/platforms causing issues , 12% and 11% chose Chrome on desktop and mobile respectively, with up to 3 choices per survey respondent.
Web developer quotes A sample of the 86 free-form survey responses relating to Chrome:
Chrome and Firefox are starting to diverge, with chrome adding features before they're fully standardized. As the dominant browser, some pages are being written to only work in chrome now. Browser compatibility is mostly OK. However the need to keep people from overusing Chrome only feature is a pain point. While this pain point can be solved by company policy, it should not have to be. Google should be more focused on the standardization process and stop forcing its way through for features that are often not ready or half baked.
Many APIs are Chrome-only and will never show up in other browsers
I don't like that Google pushes new things, seemingly without discussing it with other browser vendors and then all hipsters want to use it (regardless whether it's really useful), but it only works in Chrome and so all other browsers seem to be technically behind.
Made with FlippingBook - professional solution for displaying marketing and sales documents online