Very nice: when sharing AMP pages to iMessage or Reading List, iOS 11 Safari automatically removes AMP’s crap from the URL. Go Apple 👍 pic.twitter.com/aHgSMcofUv
Yeah, this is going to be awesome. May the web enjoy healthy browsing again.
While I may be in “AMP is bullshit” camp, I can still respect the solution it is trying to solve. I totally agree with others that it is the web developer’s responsibility to load pages fast. As John Gruber points out, it is in the interest of publishers to use AMP as Google features AMP-ready cards in search queries.
Which… is dumb. But oh well. However, when a user shares a webpage from the Safari sharesheet it will save me the headache of thinking about AMP.
Which is super awesome, because nothing sucks more than an article taking more than 15 seconds to load over “Transit Wi-fi” on the G Train. These super powered articles are literally instant, taking no more than 1 second to load — even over 4G speeds. Even after all of those pro’s Google takes it one step higher by giving search result priority to AMP powered-articles and pages for mobile searches.
So the first thing you need to do is declare in your functions.php file that you want to use a custom AMP template. Mine looks like this:
And now, the AMP will deliver your ACF content! Obviously I used Flexible Content fields in my example, but you can use any ACF field in the template-amp.php file, just make sure it validates.