This post (https://news.ycombinator.com/item?id=14536679) is an example of how AMP works. Someone has shared a link on HN. It's an AMP link, but I'm reading it on my laptop, and it's still AMP.
The end result is that all users (desktop too) are getting sent to an appified version of the page that restricts advertising/monetization options and markup options. It seems unlikely that the people who designed AMP were unaware of how this would work in practice.
I think that the core motivation for AMP has little to do with speeding up the Web, but is more about ensuring that Google's ads are delivered and so they have some say in which ad competitors are locked out.
It would be interesting to find out how much total traffic ends up on AMP pages, broken down by device type.
This post (https://news.ycombinator.com/item?id=14536679) is an example of how AMP works. Someone has shared a link on HN. It's an AMP link, but I'm reading it on my laptop, and it's still AMP.
The end result is that all users (desktop too) are getting sent to an appified version of the page that restricts advertising/monetization options and markup options. It seems unlikely that the people who designed AMP were unaware of how this would work in practice.
I think that the core motivation for AMP has little to do with speeding up the Web, but is more about ensuring that Google's ads are delivered and so they have some say in which ad competitors are locked out.
It would be interesting to find out how much total traffic ends up on AMP pages, broken down by device type.
Restricted AMP version from the HN link: https://www.geekwire.com/2017/amazon-sues-former-aws-vp-non-...
HTML version: https://www.geekwire.com/2017/amazon-sues-former-aws-vp-non-...