Live data from Hacker News

The Problem with AMP

80x24.net

101–110 of 353 posts

Re: The Problem with AMP

#101

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.

It should be what cloudflare does: clicking on the site name in the header should take the user to the non amp version of the page.

Re: The Problem with AMP

#102

It's actually a pretty nifty feature when you're browsing the web from a plane's slow wifi.

But the people who designed the page in the first place should be able to make it just as fast without using AMP.

No, only amp pages can be preloaded by google's SERP, so that is large reason it is so fast to render.

Re: The Problem with AMP

#103

I make my own amp pages by keeping JavaScript turned off on my phone. 95℅ of pages work and load instantly. Those that don't, I turn on JavaScript. If I go to those pages a lot I add them to my exception list. Sorry but I'm not an amp believer.

It just took me 8 clicks and a couple swipes to disable JS in my mobile browser, Chrome on Android. Another 8 clicks and couple swipes to enable JS. Is there a faster way to do that?

Re: The Problem with AMP

#104
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 am curious about the numbers, though i do not know internally or externally if there are numbers showing this. As a power android user, i kind of like the rss-reader-esque look and feel of the amp links. It also opens blazing fast. With these in mind, minor inconveniences (like the address bar) are probably something i wouldn't mind.

Re: The Problem with AMP

#105
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.

I actually find AMP an excellent user experience reading articles on mobile internet connections in India. Thr pages load snappily and are very responsive. The ads are not distracting etc. Among news articles, if there's AMP option, I always prefer to click it vs. others.

Re: The Problem with AMP

#106
post #63
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.

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.

As I remarked elsewhere, I actually find AMP an excellent and speedy experience. I read articles on a mobile connection in India primarily and I now invariably click AMP news story options vs. others

Re: The Problem with AMP

#107
post #63
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.

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 love amp. Loads fast. It's so fast, it almost feels native.

Re: The Problem with AMP

#108
post #92

Earlier quoted context omitted.

Controversial question: At what point would Google start to be considered an antitrust issue? I know the EU has made some noise about it, but I'm a bit surprised I haven't heard more about it here in the U.S.

In my opinion, they've already violated the trust of publishers. Take Google Lyrics for example: http://phandroid.com/2014/12/31/google-lyrics-search/ In all fairness, lyric sites were terrible. Slow, riddled with ads, and sometimes incorrect. While Google's lyrics are a great service to the user, they're at the top of search and displayed inline. There's no reason to go to lyric sites anymore. My biggest fear is Str…

And if lyric sites hosted original content, I might have felt for them. I think Google is overreaching in many ways, but not in instances like this where the content itself is such a commodity.

Re: The Problem with AMP

#109
post #63
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.

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.

Why does it matter if a user is an HN reader or not?

Re: The Problem with AMP

#110
Ugh, why does nobody ever point out that AMP and Google displaying AMP are 2 different things? Yes, Google is a huge sponsor in the AMP world but they aren't the only ones involved.

AMP itself isn't so bad- asynchronous Javascript (not no script as the article suggests) and it is still valid HTML- it just has extra properties on tags (just how Angular does).

Post reply on HN