News for hackers. Stuff that matters.
Re:Google wants websites to adopt AMP as the default for bui... by Izkata on Wednesday September 05, 2018 @08:02PM (#17922908)
> > The underlying message is clear: Google wants full equivalency between AMP and canonical URL. Every element that is present on a website’s regular version should also be present on its AMP version: every navigation item, every social media sharing button, every comment box, every image gallery.

> So Google's suggestion is that, if you've already chosen to offer an AMP page, that page shouldn't have intentionally worse usability than the original?

Take a moment to read that again. Mobile has constrained screen real-estate, constrained bandwidth, and navigation typically requires fingers covering the screen - and yet it's still supposed to support everything the full site does, and be more performant, and (it looks like) all be done in a particular framework?

Google is talking crosswise, it's no wonder AMP is a pain that only benefits Google.

Re:Google wants websites to adopt AMP as the default for bui... by ehsankia on Wednesday September 05, 2018 @08:18PM (#17922985)
I'm confused, I thought AMP was only for mobile (accelerated mobile pages). By regular version, don't they mean the regular mobile version?
Re:Google wants websites to adopt AMP as the default for bui... by Izkata on Thursday September 06, 2018 @12:06AM (#17923793)
Some quick searching to double check, it seems like not. Everything I see is referring to the "canonical" page, without really defining it in context.

But based on the way you use it, the canonical version would be whatever the primary version of the site/page is, most likely the non-mobile version (among other things, this is the URL search results would send you to [0]). It all reads like the AMP version is supposed to replace the regular mobile version.

[0] https://support.google.com/webmasters/answer/139066?hl=en#wh...