4 ms·
This post seems to conflate two ideas (1) AMP being an insufficient implementation (update-ping not working, and that being an awkward pattern anyways) and (2)
by EricBurnett 10y ago
This post seems to conflate two ideas (1) AMP being an insufficient implementation (update-ping not working, and that being an awkward pattern anyways) and (2) AMP being actively harmful to the web ecosystem in principle.
(1) Comments on the implementation I don't know nearly enough to contest. It's a new technology, and will take a lot of changes in and out of Google to get right. It's also early days - continue raising a stink about things like this and I expect it to get better quick.
(2) The principle of AMP leads to a very interesting discussion. The fact that the top-level URL users go to is not the canonical URL for the page does stray into "breaking the web" territory, at least until it's better supported in browsers. On the other hand, as I understand it that's a technical requirement for AMP to be able to verify the content served through it, which is a requirement in turn for keeping AMP page quality high (in terms of latency, etc, rather than content judgements). Which I think is the most enticing part of AMP, and not something that should be given up lightly.
I see AMP as a possible answer to the tragedy-of-the-commons problems that have resulted from standardizing on third party display ads for monetization, third party scripts for analytics, etc. Giving someone else a hook into your page that isn't incentivized to keep it fast and reliable leads to an end state where publishers have no reason to clean up the experience on their own sites because that'd cost them money, and because the bad experience on every other site prevents them from being commensurately rewarded for being a good player. (E.g. adblockers affect every site equally). And the third party tech providers have no incentive to fix things for similar reasons - alternative providers out there would cause the same poor user experiences anyways, and make more money from doing so and enabling them to sell to publishers better. If we cannot rely on principled actions from publishers or tech providers, how does the experience of the web get better enough broadly?
AMP to me is an answer to that - maybe not the best answer, but the most viable one I've seen so far. It allows for direct control of what is/isn't possible, and if it gains traction may have enough clout to push for some of those better experiences that aren't arising naturally.
The other possible answers I see don't seem to be working better. Relying on regulation seems destined to failure; user experience is too messy to craft rules around, and nobody is placed to enforce them globally. Relying on common gatekeepers seems to be failing - Google algorithm changes worked for a while to incentivize page quality, but I don't think Facebook is (or should?) making equivalent judgements about the quality of content users link to for ranking purposes, and it seems even harder to enforce in other direct-user-sharing sites like Twitter.
[Edit] Disclaimer: I work for Google, in Technical Infrastructure. I used to be in Ads, though not related to AMP.
- gorhill 10y ago> AMP to me is an answer to that With such statement, it would be appropriate you disclose up front that your employer is Google[1]. [1] http://www.thelowlyprogrammer.com/ http://www.thelowlyprogrammer.com/
- EricBurnett 10y agoMy apologies. I work at Google, used to be in Ads (not AMP), these days I'm in Technical Infrastructure.
- tinodotim 10y ago>I used to be in Ads, though not on AMP. Maybe I misread that, but for me it sums AMP up in quite a good way: It's not really about making the web better, it's about more admoney for Google, if a former ads guy has to point out he didn't work on the AMP project there ;)
- EricBurnett 10y agoYou read correctly, but it also doesn't tell the full story. I've edited to be "not related to AMP" to try to convey this better. In short: AMP itself is not part of Ads, but there is a group within Ads focussing on AMP - because one of the biggest blockers to AMP adoption is (was?) getting ads supported within the model.
- invisible 10y agoAlthough in theory AMP makes sense, I think the issue is actually more broad than just mobile. On desktop, lots of people rely on an ad blocker to make sites usable again. That mobile doesn't have a way to block ads is probably a failure of Google, Apple and other players to allow extensions. Google has a majority share of the first impression for ads so it's hard for me to really understand how they can't just strong arm other advertisers and other networks into having better ads. Maybe that's the AMP play but it's a pretty weak appeal to consumers and (as evident from this thread) publishers. Ad blockers proliferating are a response to this inaction in my mind.