Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

You can't disable Google AMP

productforums.google.com

Post reply on HN
Print view View original

41–50 of 81 posts

Re: You can't disable Google AMP

#41

Post by millstone »

Lazare wrote: post #12

As a user, I've found AMP results to be invariable an excellent user experience on mobile. I will always click an AMP link over a non-AMP link, when on mobile, because I know the AMP link will load quickly and be usable, and the odds are good the non-AMP link will not. Apparently this is a minority view around here. :)

My specific gripes around AMP as an iPhone user:

1. Scrolling momentum is very different, making it feel non-native

2. The URL bar doesn't hide normally. Scroll down in portrait mode and it doesn't hide.

3. The URL bar doesn't un-hide normally. Switch to landscape mode and scroll up, the URL bar does not reveal itself.

4. Safari Reader mode often doesn't work.

5. Scrolling before the page is done loading can make it look like there's less content then there actually is.

6. Some dynamic sites misbehave (e.g. reddit does not show me as logged in).

7. Copying the URL results in some Google thing instead of the real URL

8. Relationship between AMP X close button and Back button is confusing

I am curious which of these you experience, which you don't notice, and which you don't experience at all if you are an Android user?

Re: You can't disable Google AMP

#42

Post by CaptSpify »

mdasen wrote: post #20
Lazare wrote: post #12

As a user, I've found AMP results to be invariable an excellent user experience on mobile. I will always click an AMP link over a non-AMP link, when on mobile, because I know the AMP link will load quickly and be usable, and the odds are good the non-AMP link will not. Apparently this is a minority view around here. :)

It totally is a great experience. The page loads fast without too much crap. But it's also sad that something not-quite-open is taking over an important part of the web. AMP is this Google-wrapped version of a part of the web that tries to keep you in Google's land rather than allowing you to browse the site you visited. As a user, I like clicking on AMP links. But in a certain way, it's like eating candy. I know it'…

And this is why I dislike AMP. Instead of doing the right thing and rewarding good sites, Google instead is using the opportunity to push everyone into their ecosystem. The better solution is to encourages sites to think about their design and reward them accordingly.

Re: You can't disable Google AMP

#43

Post by ajdlinux »

Lazare wrote: post #12

As a user, I've found AMP results to be invariable an excellent user experience on mobile. I will always click an AMP link over a non-AMP link, when on mobile, because I know the AMP link will load quickly and be usable, and the odds are good the non-AMP link will not. Apparently this is a minority view around here. :)

As a user who's often on a moderate-bandwidth 3G connection in Australia I can't say I've had any problems with AMP so far.

Re: You can't disable Google AMP

#44

Post by CaptSpify »

seanwilson wrote: post #31

I can understand how the aspect of the control Google has over AMP isn't ideal but you can't deny AMP sites are a great user experience on mobile. Pages tend to load for me in less than 0.5 seconds even on my mobile connection. For other sites, pages can take 10 to 30 seconds to load, have pop-ups, image loading causes the page the jump up/down etc. Making sites with small download sizes and quick rendering is a very…

The problem that AMP is trying to solve is definitely real. But pushing sites to add another layer on their system is the wrong way to do it, IMO. Why don't they just start rewarding systems that load fast, instead of pushing people into another google system?

Re: You can't disable Google AMP

#45

Post by technion »

detaro wrote: post #40
technion wrote: post #39

The thing about AMP is that it takes work. You cannot just install an AMP plugin and expect your existing website to suddenly serve AMP. However, with certain CMS's, that's exactly how things are marketed. So what we're seeing is people go off and buy themes or whatever to make their website look the way they want, then they install some plugin and say "done". And then they are taken by surprise when, on mobile, thei…

The question then of course is: why is the non-AMP version of your blog slower, and could you have improved that with the same effort? Or is it just that people coming there via Google get Googles CDN which is faster?

The easy answer is that AMP forces you to do things like always declaring image height and width. And yes I could do that without AMP, but the moment you're not forced to do something, the path of least resistance is to not bother.

I certainly never would never have bothered setting up a build process to inline CSS previously.

Re: You can't disable Google AMP

#46

Post by semi-extrinsic »

cramforce wrote: post #27
CaliforniaKarl wrote: post #26

Earlier quoted context omitted.

I don't think it's a minority view. At least in my case, I'm fine with clicking on an AMP link, but I'm always aware of: * How difficult it will be if I want to share the link with someone (because I don't want to share an AMP link). * How difficult it is if I want to go exploring around the site that has the thing I am reading.

We are working on a direct path from AMP pages loaded from Google Search to the canonical to fix the link issue & sharing will use the canonical link where technically possible.

While you're at it, why not add "straight links" to normal Google results so they can be copied as well? The current situation having everything be a Google referral link is a pain in the neck and users go out of their way to avoid copying those.

Re: You can't disable Google AMP

#47

Post by flukus »

biot wrote: post #19

The place to complain about AMP isn't Google... it's the sites that AMP-enable their content. If enough people tell publishers "I've stopped reading your site because of AMP" maybe they'll take notice.

How many supported AMP because the wanted to? Google has way to much control over the modern web, they're approaching abusive monopoly status.

Re: You can't disable Google AMP

#48

Post by ec109685 »

detaro wrote: post #40
technion wrote: post #39

The thing about AMP is that it takes work. You cannot just install an AMP plugin and expect your existing website to suddenly serve AMP. However, with certain CMS's, that's exactly how things are marketed. So what we're seeing is people go off and buy themes or whatever to make their website look the way they want, then they install some plugin and say "done". And then they are taken by surprise when, on mobile, thei…

The question then of course is: why is the non-AMP version of your blog slower, and could you have improved that with the same effort? Or is it just that people coming there via Google get Googles CDN which is faster?

AMP preloads the content before you click, which your own web site can't compete with.

Re: You can't disable Google AMP

#49

Post by technion »

vmarsy wrote: post #14
lovich wrote: post #10

Like the other commenters here, I really disliked amp for a variety of reason such as the bar on top and the inability to easily link the main version of the page. However, I'be come to feel that we've brought this on ourselves as Web developers by making every website incredibly bloated and only possible to use on high speed connections. I've spent the past month in thailand on a much slower connection and the only…

> the only sites I can reliably use currently are text sites like hacker news and amp pages. I can have a site like reddit even take 30-40 seconds to load. What about reddit's AMP pages [1]? [1] https://redditblog.com/2016/09/20/amp-and-reactredux/

That blog reads as contradictory.

It talks about building a SPA, and rendering on the client side using JavaScript. It also talks about being AMP compliant.

Those goals cannot coexist.

Re: You can't disable Google AMP

#50

Post by saurik »

snowwrestler wrote: post #4

To be clear, this is referring to the client side--that is, from the perspective of mobile web searchers, you can't ask Google to hide AMP results from the results page. To my knowledge, publishers still have to opt into participating in Google AMP, and I assume they can opt out? That was my fear in reading the headline--that publisher participation in AMP is irrevocable, which would be bad.

If you stop doing AMP, won't all of the non-canonical/duplicated/evil amp.google.com URLs users have now shared and linked to your content going to break, meaning that once you go AMP you are effectively trapped?
Post reply on HN