A good idea gone bad. So much hate for Google’s Accelerated Mobile Pages (AMP). Sorry mobile web!
franze
I implemented AMP on my own project and we implemented it at some clients ... all regret it.
The bounce rate, time on site, average page views of AMP pages is always worse than on the responsive version. And as we now have responsive webpages + an AMP version to maintain the overall project costs got higher. Additional the AMP pages are already falling behind as devs and management just hate them.
And outside of the news vertical we haven't seen any major positive traffic impact (and as stated above, the usage values of the AMP-traffic is crap.)
Also we spoke with some users and they all were confused of "what happened to our site...".
AMP is a horrible idea with an even worse implementation.
saycheese
There is zero reason for AMP to be hijacking URLs or embedding any additional elements into a page that are detectable by the average user.
Beyond that, universal opt-out should be possible and stats on the percentage of users opting out should be published real-time.
As such, until this is addressed, I am against AMP.
ClassyJacket
It also sucks if you want to interact with the page, since, inanely, you can't click through to the real page.
monochromatic
The silliest part is that clicking the x in the AMP bar doesn't redirect you to the real page... it just takes you back to your search results.
fragmede
You have a valid point about page bloat, but its a distraction and a poor excuse for hijacking the entire web. My hate for AMP is because Google is using its might to break a fundamental contract for how the web works - the URL bar shows what site you're on, and content is coming from that domain.