If you have one of the latest mobile phones, you likely have seen AMP results when news results are displayed. But for those with older smart phones, AMP results might not be displayed… and arguably, it is those older – and often slower – phones could benefit from AMP even more than those with the latest and greatest models.
At SMX, Dave Besbris confirmed that Google tried to make AMP compatible with the latest versions of all mobile browsers – and this include iOS Safari – but that they are still working on making older phones AMP compatible too.
The AMP project is aiming for AMP compatibility for browsers with at least a 1% market share, as well as the latest two versions of the most recent Chrome, Firefox, Edge, Safari and Opera.
In general we support the 2 latest versions of major browsers like Chrome, Firefox, Edge, Safari and Opera. We support desktop, phone, tablet and the web view version of these respective browsers.
Beyond that the core AMP library and builtin elements should aim for very wide browser support and we accept fixes for all browsers with market share greater than 1 percent.
In particular, we try to maintain “it might not be perfect but isn’t broken”-support for the Android 4.0 system browser and Chrome 28+ on phones.
Of course, different platforms that these browsers are on can cause difficulty. For example, AMP only began showing in the iOS version of Chrome last week. And it still isn’t being displayed in Google Search App (aka Google Now) for iOS users.
It is good to see that they are continuing to work on older browsers for older phones that might not be capable of using the latest versions of browsers.
— Jennifer Slegg (@jenstar) March 1, 2016
Latest posts by Jennifer Slegg (see all)
- Removing Links from Disavow to Recover Google Rankings - July 28, 2016
- Using Nofollow on Navigation for Crawl Budget Reasons - July 27, 2016
- Expanded Text Ads Now Available in Google AdWords - July 26, 2016
- Google AdWords Launches Device Bid Adjustments - July 26, 2016
- No PageRank Loss for 30x Redirects, Including 301 & 302 Redirects - July 26, 2016