2 ms·

> where they control the content and give the providers whatever revenue they consider "fair" AMP doesn't give Google any control over content or revenue. It s

> where they control the content and give the providers whatever revenue they consider "fair" AMP doesn't give Google any control over content or revenue. It supports hundreds of different ad networks, not just Google's: https://www.ampproject.org/docs/reference/components/amp-ad#supported-ad-networks https://www.ampproject.org/docs/reference/components/amp-ad#... > and provide a friendly, uniform interface AMP doesn't enforce a uniform interface. Its restrictions are primarily technical; not stylistic.

saagarjha 8y ago
> AMP doesn't give Google any control over content or revenue. It gives Google control over serving the content and how it's ranked when users search for it. That's quite a bit of sway, I'd think. > AMP doesn't enforce a uniform interface. Its restrictions are primarily technical; not stylistic. Most AMP pages look very similar to me. That's not necessarily a bad thing, but it does suggest that there might be some sort of technical hurdle to make content that deviates from the standard layout that Google recommends.
- Ajedi32 8y ago
  > It gives Google control over serving the content Fair point. They're planning to fix this with the upcoming Web Package Standard though, so it won't be an issue for much longer. > and how it's ranked when users search for it That's just as true for non-AMP content. > Most AMP pages look very similar to me. AMP provides a bunch of prebuilt components developers can use to construct their pages, so I suspect what you're noticing here is developers just taking the path of least resistance. (Kinda like how sites built with Bootstrap tend to look similar.) With a little effort, AMP pages _can_ differentiate themselves. For example, these are all AMP pages: * https://tasty.co/ https://tasty.co/ * https://magebit.com/ https://magebit.com/ * https://www.myntra.com/amp/lipstick https://www.myntra.com/amp/lipstick

saagarjha 8y ago

> AMP doesn't give Google any control over content or revenue. It gives Google control over serving the content and how it's ranked when users search for it. That's quite a bit of sway, I'd think. > AMP doesn't enforce a uniform interface. Its restrictions are primarily technical; not stylistic. Most AMP pages look very similar to me. That's not necessarily a bad thing, but it does suggest that there might be some sort of technical hurdle to make content that deviates from the standard layout that Google recommends.

Ajedi32 8y ago
> It gives Google control over serving the content Fair point. They're planning to fix this with the upcoming Web Package Standard though, so it won't be an issue for much longer. > and how it's ranked when users search for it That's just as true for non-AMP content. > Most AMP pages look very similar to me. AMP provides a bunch of prebuilt components developers can use to construct their pages, so I suspect what you're noticing here is developers just taking the path of least resistance. (Kinda like how sites built with Bootstrap tend to look similar.) With a little effort, AMP pages _can_ differentiate themselves. For example, these are all AMP pages: * https://tasty.co/ https://tasty.co/ * https://magebit.com/ https://magebit.com/ * https://www.myntra.com/amp/lipstick https://www.myntra.com/amp/lipstick