3 ms·
As someone who has maintained an AMP implementation for a big (albeit non-news) site for years, I think "AMP does not allow as much customization of ads as pape
by nightpool 5y ago
As someone who has maintained an AMP implementation for a big (albeit non-news) site for years, I think "AMP does not allow as much customization of ads as papers are used to" is a feature, not a bug. There are constant demands from sales and advertising partners to add more and more disruptive and broken web experiences, and having a bedrock of "Google will penalize us if we do this" to fall back on is really, really important.
I don't care whether AMP "helps publishers"—I think AMP holds publishers accountable for their (accidental or careless) UX disasters, and prevents them from happening in the first place.
- Spivak 5y agoI mean relying on a massive corporation's total dominance over the web and semi-arbitrary rules for reward and punishment in order to tell the "business" side of your company no isn't exactly something I would be touting as a positive thing. All of this crap is because sw engineers don't have a professional association with an ethics board. Can you imagine if you could put the experience of your users first and tell your business to fuck off when they ask for this nonsense secure that they really can't just fire you and find someone who will sell out.
- nightpool 5y agoI invite you to find any ethics board in the world that would speak out against "I made my company $10MM more yearly by causing the page to load 3 seconds slower for all of our users, with janky scrolling and popup ads". I mean, frankly, that's a very utilitarian calculation—think about just the simple case of a business saving money by removing their caching layer. Who is to say how many seconds of performance deoptimization is worth how many dollars of saved cost? If it only cost users 0.1 seconds in the median case and 1 seconds in the 95th percentile case, and you saved $1MM yearly, would you make that call?
- uncomputation 5y agoThe way I see it, the constant pressures from ads departments is the issue and having to make an appeal to Google is not a good solution. We should not have to rely on having Google back us up on what constitutes a “good” page. So, I don’t agree that it’s “really, really important.” If anything, it’s a sad picture of digital journalism. I think what’s really, really important is having the freedom to design your site without having to worry about Google’s arbitrary judgment of that design and not needing to rely on pleasing a search engine to show up in its results. AMP definitely does not hold anyone accountable. Look at Reddit. Absolutely atrocious UX after AMP from what is just a basic forum. Instead, AMP makes everyone - regardless of content, design, or purpose - obey the same Google-approved standard of design, using Google-approved fonts and Google-approved CSS. In my view, AMP is the UX disaster because I hate the way it looks and have to remove the AMP from every news article I read. Oftentimes, publishers have a better idea of how their content should look than Google does. Especially smaller ones which have a strong focus on design.
- nightpool 5y ago> Google-approved fonts and Google-approved CSS This is just completely false. You can use webfonts and custom CSS on AMP. There are some common-sense limitations, like limiting the total size of the CSS, but I've never run into an issue where I had a design that I couldn't achieve on AMP due to CSS constraints. > the constant pressures from ads departments is the issue The problem is that sales departments don't work in isolation—they're beholden to the broader pressures of the marketplace. It's a classic coordination problem—the industry is caught in a race-to-the-bottom of ad quality, and as long as you can make a few extra bucks per month by adding more and more intrusives ads, you're going to do so. Google has the ability to set different incentives for publishers, because they control a lot of traffic, which turns into revenue.