Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
Google

The Problem With Google AMP (80x24.net) 56

Kyle Schreiber has raised some issues about Google's AMP (Accelerated Mobile Pages), an open source project unveiled by the company in 2015 with which it aims to accelerate content on mobile devices. He writes on his blog: The largest complaint by far is that the URLs for AMP links differ from the canonical URLs for the same content, making sharing difficult. The current URLs are a mess. They all begin with some form of https://wwww.google.com/amp/ before showing a URL to the AMP version of the site. There is currently no way to find the canonical link to the page without guessing what the original URL is. This usually involves removing either a .amp or ?amp=1 from the URL to get to the actual page. Make no mistake. AMP is about lock-in for Google. AMP is meant to keep publishers tied to Google. Clicking on an AMP link feels like you never even leave the search page, and links to AMP content are displayed prominently in Google's news carousel. This is their response to similar formats from both Facebook and Apple, both of which are designed to keep users within their respective ecosystems. However, Google's implementation of AMP is more broad and far reaching than the Apple and Facebook equivalents. Google's implementation of AMP is on the open web and isn't limited to just an app like Facebook or Apple.
This discussion has been archived. No new comments can be posted.

The Problem With Google AMP

Comments Filter:

System checkpoint complete.

Working...