Live data from Hacker News

You Don't Get AMP

blog.153.io

31–37 of 37 posts

Re: You Don't Get AMP

#31

Earlier quoted context omitted.

What does amp give me that a non-js page can't? Also, applications aren't the target for amp.

Can you write a carousel without JS? A live blog? Lazy loading images and ads? A stateful e-commerce product page? Have a look through the list of AMP components, you'll be surprised what's possible. https://www.ampproject.org/docs/reference/components

We can have all of that and have sub 100ms render times without AMP, we just have to cut out all the bloated javascript and trackers everywhere.

Google loves AMP because they (and only they) get to still track users.

Re: You Don't Get AMP

#32

As someone who has developed for mobile web, it can be surprisingly hard to push back on bloat from marketing / seo / analytics teams. I hope this becomes a W3C standard so us developers can show them the finger the next time they want to bring mobile web to a crawl.

Does Google not have any guidelines that say to keep pages small and fast? Seems like they should have a list of things to keep in mind when looking at search-rankings

Re: You Don't Get AMP

#33
post #31

Earlier quoted context omitted.

Can you write a carousel without JS? A live blog? Lazy loading images and ads? A stateful e-commerce product page? Have a look through the list of AMP components, you'll be surprised what's possible. https://www.ampproject.org/docs/reference/components

We can have all of that and have sub 100ms render times without AMP, we just have to cut out all the bloated javascript and trackers everywhere. Google loves AMP because they (and only they) get to still track users.

> they (and only they) get to still track users

Wrong. https://www.ampproject.org/docs/reference/components/ads/amp...

Re: You Don't Get AMP

#34

As someone who has developed for mobile web, it can be surprisingly hard to push back on bloat from marketing / seo / analytics teams. I hope this becomes a W3C standard so us developers can show them the finger the next time they want to bring mobile web to a crawl.

Does Google not have any guidelines that say to keep pages small and fast? Seems like they should have a list of things to keep in mind when looking at search-rankings

It does, although only can only assume the effect of performance on search rankings. It's non-tangible metric as far as revenue is concerned.

Re: You Don't Get AMP

#35
post #31

Earlier quoted context omitted.

We can have all of that and have sub 100ms render times without AMP, we just have to cut out all the bloated javascript and trackers everywhere. Google loves AMP because they (and only they) get to still track users.

> they (and only they) get to still track users Wrong. https://www.ampproject.org/docs/reference/components/ads/amp...

Am I misunderstanding this? It looks you you have to request the tracking data from them?

Re: You Don't Get AMP

#36

Earlier quoted context omitted.

Does Google not have any guidelines that say to keep pages small and fast? Seems like they should have a list of things to keep in mind when looking at search-rankings

It does, although only can only assume the effect of performance on search rankings. It's non-tangible metric as far as revenue is concerned.

Then what would be the difference between showing them the AMP standards, and just pointing them to those documents?

Re: You Don't Get AMP

#37

Earlier quoted context omitted.

For now. AMP is a PROXY/MITM service, with all the perks that come from being such a service. There is nothing stopping google ,or whatever company owns them after they become a Yahoo!, from changing their "policy" to better be aligned with their interests.

As soon as Google stops providing value to publishers, they lose their power in the industry. For now, we work with what we have.

> As soon as Google stops providing value to publishers, they lose their power in the industry

As soon as Google stops providing value to publishers, they are the industry.

Post reply on HN