Accelerated Mobile Pages - a quick reaction (no js)
Today Google launched the Accelerated Mobile Pages Project:
The Accelerated Mobile Pages (AMP) Project is an open source initiative that embodies the vision that publishers can create mobile optimized content once and have it load instantly everywhere.
Which sounds very much in tune with indieweb goals, so I had a quick look. My first reaction was one of shock, as it said SVG was banned:
Hang on a second, AMP claims to be about mobile responsiveness, but bans SVG? What fuckery is this? https://t.co/fF4q8SNPHZ— Kevin Marks (@kevinmarks) October 7, 2015
However, google responded that they had forgotten to update the pubic spec and most SVG is supported.
Phew. Thanks, .
That fits in with Tantek's js;dr point of view to some extent, except they leave loophole for their own js code, which while fast and well written compared to most ad content, still breaks some things.
They also require a lot of arbitrary weird markup (like emoji in the html element, which violates content encoding, a weird style incantation that makes the page opaque, and require the proprietary schema.org markup.
There is no good reason to use amp-video or amp-audio over video or audio tags- the reason given for img—that AMP want control over preloading—is already present in audio and video tags, as you can just set preload=none on the tag itself. Here's a page with lots of hi-def videos that loads rapidly, and waits for you to hit play.
Talking of video, I discussed AMP with Jeff Jarvis and Leo Laporte on TWiG this week:
Jeff's perspective that this is a way to get publishers out from under the weight of their accumulated adtech debt, and to get their articles out elsewhere on the web is a important one, as is Leo's reluctance as a publisher to change all his site templates again to conform to this.