Live data from Hacker News

The Problem with AMP

80x24.net

131–140 of 353 posts

Re: The Problem with AMP

#131
post #6

AMP is one of the most frustrating experiences I've had with Google. the fact that it's foisted on users, with no option to disable it, makes it borderline infuriating. If you're stuck on an AMP page in your mobile browser, you can click on the browser's "Request desktop site" option to load the full page.

amphtml links on non-google domains, e.g., newspapers, etc., are great for text only browsers.

If I didn't know this was for mobile browsers I would think it was a gift to blind users who do not use GUIs.

amphtml links also provide an easy way around paywalls, most of the time.

I have no idea what is the true purpose of these amphtml links. It sounds like it's some advertising nonsense.

As a text-only browser user I see no ads and experience no page load delays, but I do see how overstuffed web pages have become.

In this regard, amphtml is a breath of fresh air.

Re: The Problem with AMP

#132
post #70
post #63

Earlier quoted context omitted.

I am really curious if an ordinary user gets frustrated with AMP as much as an HN reader does. PS: Not intending to be sarcastic. PS2: I work for google, but not on something amp related.

I've seen ordinary users get frustrated with it, but they don't understand why. They don't know what AMP is, and they don't realize they are on an AMP page. For example, the URL bar says they are on Google but they are reading a Slate article. The web is already confusing enough, and AMP makes it worse. Many ordinary users think they are reading content from Google, like that famous CNN interview where a lady said, "…

I've seen people say about "fake news" articles that have google.com as the top domain (because AMP) as an indicator of some reliability. Google is unintentionally, but actively, harming their image by being associated with and promoting such content.

Re: The Problem with AMP

#133
I wrote a similar(although not as concise) article about 3 month ago: https://www.alexkras.com/google-may-be-stealing-your-mobile-...

After which I was invited to meet Google AMP team and to express my concerns, you can read my Q&A here: https://www.alexkras.com/i-had-lunch-with-google-amp-team/

TLDR; A lot of concerns are getting addressed

1. Minor, but the bar at the top is now scrollable on all devices, including (finally) iOS: https://www.alexkras.com/amp-toolbar-is-now-scrollable-on-sa..., it was not when I first wrote the article, so it's a good sign.

2. It is my understanding that the team is actively working on a way to "fix" the link issue, and give an easy way to get to original article, although it remains to be seen how they will approach it.

3. You can opt out from AMP cache on the web site end, but it really defeats the purpose. Read more here: https://www.alexkras.com/i-had-lunch-with-google-amp-team/

4. Most importantly, looks like there is even internal pressure to give people an option to Turn Off AMP on the search engine side, if they don't like it. See this, for example: https://twitter.com/slightlylate/status/820344221450125312 @cramforce is THE tech lead on AMP and @slightlylate is also a big shot at Google on Chrome Team.

Personally, I have mixed feelings about AMP, on one side I really like the speed, on the other I hate how it breaks the Web as we know it.

Re: The Problem with AMP

#134
post #70
post #63

Earlier quoted context omitted.

I am really curious if an ordinary user gets frustrated with AMP as much as an HN reader does. PS: Not intending to be sarcastic. PS2: I work for google, but not on something amp related.

I've seen ordinary users get frustrated with it, but they don't understand why. They don't know what AMP is, and they don't realize they are on an AMP page. For example, the URL bar says they are on Google but they are reading a Slate article. The web is already confusing enough, and AMP makes it worse. Many ordinary users think they are reading content from Google, like that famous CNN interview where a lady said, "…

>Which leads to the question, why is google doing this?

Money. Amp vs adblockers

Re: The Problem with AMP

#135

On AMP page, clicking the X on the header box should load the HTML page. Instead it kicks you back to the search results. I think I would be okay if they fixed that one thing.

That's my main pet peeve with AMP as well. In my mind the [x] in the top bar is almost exclusively associated with 'remove the bar' behavior in Safari on iOS.

They viewed Google as platform and clicking x, takes user back to the platform. This was one of my biggest complains about the AMP project form the start. According to AMP team lead, however, the user testing on regular (not tech) users showed, that x did what people expected.

I really think AMP can benefit a lot from PR stand point by letting techies opt out from it, but leaving it on for "regular" users. See https://twitter.com/slightlylate/status/820344221450125312

Re: The Problem with AMP

#136
post #29

One thing I love about AMP, that seems to never be mentioned when people discuss it, is viewing AMP-HTML pages on my laptop. I wrote a small chrome extension that always forwards my page to the equivalent AMP page (if one exists) and the experience of reading the news is so much better. AMP pages off mobile are really really amazing. Compare Non-AMP[0] vs AMP[1] [0] http://www.sfgate.com/bayarea/article/Trump-on-the-…

The only difference that I can see is that they didn't provide a pop up video on the amp version. I'd never use a site that forces me to load and click away a video on mobile anyway, not sure this has anything to do with AMP.

Re: The Problem with AMP

#138

Our early data is showing that advantages like Search engine ranking and reduction in bounce rate are making AMP a necessity in 2017. All the content gateways have their own proprietary format to keep users locked into the platform it's a smart move. You can read more advantages at http://alphapages.io

The mobile page allows scrolling to sides and the headers/features are hardly readable

Re: The Problem with AMP

#139

I wrote a similar(although not as concise) article about 3 month ago: https://www.alexkras.com/google-may-be-stealing-your-mobile-... After which I was invited to meet Google AMP team and to express my concerns, you can read my Q&A here: https://www.alexkras.com/i-had-lunch-with-google-amp-team/ TLDR; A lot of concerns are getting addressed 1. Minor, but the bar at the top is now scrollable on all devices, including…

The navigation toolbar hiding is only part of the problem with the navigation on iOS: AMP also breaks the default iOS navigation bar hiding, so even with the AMP toolbar hiding screen real estate is still being burned. Your article also hadn't even mentioned scrolling: on iOS, at least, scrolling is "janky" and slow and unnatural; and that's before you realize the insanity of how they selfishly are breaking scroll left and right in their attempt to take control of the entire Internet as mere content for their website :/.

Re: The Problem with AMP

#140
post #139

I wrote a similar(although not as concise) article about 3 month ago: https://www.alexkras.com/google-may-be-stealing-your-mobile-... After which I was invited to meet Google AMP team and to express my concerns, you can read my Q&A here: https://www.alexkras.com/i-had-lunch-with-google-amp-team/ TLDR; A lot of concerns are getting addressed 1. Minor, but the bar at the top is now scrollable on all devices, including…

The navigation toolbar hiding is only part of the problem with the navigation on iOS: AMP also breaks the default iOS navigation bar hiding, so even with the AMP toolbar hiding screen real estate is still being burned. Your article also hadn't even mentioned scrolling: on iOS, at least, scrolling is "janky" and slow and unnatural; and that's before you realize the insanity of how they selfishly are breaking scroll le…

Great points!
Post reply on HN