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.
The Problem with AMP
101–110 of 353 posts
Re: The Problem with AMP
#102It'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.
Re: The Problem with AMP
#103I 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.
Re: The Problem with AMP
#104Earlier 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, "…
Re: The Problem with AMP
#105AMP 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.
Re: The Problem with AMP
#106AMP 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.
Re: The Problem with AMP
#107AMP 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.
Re: The Problem with AMP
#108Earlier 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…
Re: The Problem with AMP
#109AMP 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.
Re: The Problem with AMP
#110AMP 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).