...
Browser | Share of Reckitt websites users, % | Market share worldwide, % | Market share in India, % | Market share in China, % | Market share in Asia, % | Market share in North America, % | Market share in Europe, % | |
---|---|---|---|---|---|---|---|---|
1 | Chrome | 52.00 | 63.51 | 87.09 | 49.83 | 72.6 | 51.44 | 58.88 |
2 | Safari | 26.00 | 19.32 | 2.87 | 11.07 | 12.53 | 33.82 | 20.33 |
3 | Android Webview | 11.00 | n/a | n/a | n/a | n/a | n/a | n/a |
4 | Safari (in-app) | 5.00 | n/a | n/a | n/a | n/a | n/a | n/a |
5 | Samsung Internet | 3.00 | 2.83 | 1.42 | n/a | 2.96 | 2.03 | 3.39 |
6 | Edge | 1.00 | 4.08 | 1.03 | 4.66 | 2.54 | 5.87 | 5.64 |
7 | Firefox | 1.00 | 3.90 | 1.64 | 3.08 | 1.95 | 3.54 | 5.86 |
8 | Opera | 1.00 | 2.26 | 2.90 | n/a | 1.73 | 0.85 | 3.09 |
9 | YaBrowser | 0.00 | n/a | n/a | n/a | n/a | n/a | 0.68 |
10 | UC Browser | 0.00 | 0.85 | 2.03 | 11.65 | 1.87 | n/a | 0.13 |
11 | Amazon Silk | 0.00 | n/a | n/a | n/a | n/a | n/a | n/a |
12 | Mozilla Compatible Agent | 0.00 | n/a | n/a | n/a | n/a | 0.19 | n/a |
13 | Internet Explorer | 0.00 | 0.44 | 0.05 | 0.85 | 0.40 | 0.59 | 0.35 |
14 | EnfaMobileApp | 0.00 | n/a | n/a | n/a | n/a | n/a | n/a |
15 | Coc Coc | 0.00 | n/a | n/a | n/a | n/a | n/a | n/a |
16 | Android Browser | 0.00 | 0.65 | n/a | 0.64 | 0.83 | 0.74 | 0.37 |
17 | Opera Mini | 0.00 | n/a | n/a | n/a | n/a | n/a | n/a |
18 | Puffin | 0.00 | n/a | n/a | n/a | n/a | n/a | n/a |
19 | [FBAN | 0.00 | n/a | n/a | n/a | n/a | n/a | n/a |
20 | Android Runtime | 0.00 | n/a | n/a | n/a | n/a | n/a | n/a |
* - All data are taken from https://gs.statcounter.com/browser-market-share/
...
Additional takeaways
At the top end, the design and functionality should mirror expectations, then with less important browsers we can deviate on design but still offer the functionality, then we compromise the functionality down to base and then there will be a bunch of browser variants that aren’t specifically tests but at the very worst, serving only HTML should still provide base level value.
Regional differences should be taken into account ( for example, QQ browser doesn’t show up much on a global scale, but it can represent 10%+ of traffic in some markets (China/India) etc).
We don’t need to support browsers to a strong extent when their manufacturers don’t support them already (e.g. IE. Base experience only).
Including JAWS into support will require having a license.
Regarding overall browser support, as we are to use progressive enhancement approach with the semantically correct HTML first and CSS on top, then we need to have basic support for most of the browsers.
Regarding screen sizes, we probably should define breakpoints rather than names of the screen sizes. . Screen dimensions are only one attribute.
We need to design with minimal breakpoints and breaking based on the content, not the device.