"We could do that, but then we'd lose the special AMP placement on Google SERPs" is a much more compelling argument, and preferable to starting a proxy war between the CMO and the CTO.
Google has done a hell of a job flexing their Search muscles to encourage the behavior they want, here. All the while somehow open-washing the project so that SEO-types make the ridiculous statements you quoted, implying that AMP isn't a Google owned-and-run project.
On an engineering level, I respect AMP. From an anti-competitive / social engineering perspective, it's absolutely terrifying.
For more details, you can read the (very readable) AMP docs: https://www.ampproject.org/docs/guides/how_cached
Here’s the section on guidelines for implementing an AMP cache: https://github.com/ampproject/amphtml/blob/master/spec/amp-c...
Google engineers seem to have a hard time differentiating between a platform and a framework. PWAs and suffer from the exact same problem. They’re great if you build a greenfield product to their exact specs, but difficult to use otherwise.
How is limiting size and server round-trips of CSS not related to the problem being solved by AMP?
I take a look at the average mobile web page and thank Google that AMP brings sone restrictions.
From a technical standpoint it wouldn't surprise me if people start proposing binary formats that beat text/plain + gzip in size and speed.
Webassembly
That's exactly what they are doing with Instant Apps, they just try different strategies to control the web more at the same time.
Airbnb really doesn’t.
There's many downsides, but, for example...Google carousel results inject JavaScript that allows the end customer to left or right swipe right to a competitor...if you choose the AMP path.
I'm not clear on why Google doesn't give control of the top banner to publishers.
It's a growth hack to get better organic search traffic, with user experience performance improvements a secondary concern.
When a big company like Airbnb jumps on a technology bandwagon people notice, and write-ups like this influence the choices other organisations make. They could at least just be upfront about the reasons why they're doing it.
The search benefit isn't even a long-term one: Either AMP will go away for some reason at some point, or, if the status quo is maintained, everyone will be forced to use AMP by Google's search monopoly, rendering it a null benefit to your rankings as everyone else transitions to it.
> it's very unlikely that Airbnb wants to admit they're probably being paid for it or getting some other form of special consideration for writing this.
It doesn't look like anyone from Airbnb wrote this. But you're right, that's a good strategy - instead of the accommodation and experiences thing, they should implement AMP and get paid by Google for it. That's how business works: https://i.imgur.com/Vd6gI7X.jpg?1h
Congratulations Brian and Gil on implementing this!
Maybe in the long term, but meanwhile they get the benefits for being early adopters. If AMP fails, they will simply roll back.
The reason to use AMP is SEO. If you want literally any benefit other than SEO, just improve the performance on your own mobile site. Then you won't have to jump through weird hoops and come up with entirely new "magic carpet" user flows, because you'll actually control your own content on your own site.
The talk attached to this Medium piece was given at "TechSEO Boost", but the article itself dances around ever using the term. So we're left to wonder why AirBnb is very worried about being able to link users to their native app, while they apparently don't care at all about whether users are using their web site. It's because of SEO.
> the Accelerated Mobile Pages (AMP) project, which has some powerful backers including Google
> It would be fair to say that Google has been a very vocal supporter of the initiative from day one.
These are really weird ways of describing a Google-owned, Google-pushed initiative.