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

The Problem with AMP

80x24.net

Post reply on HN
Print view View original

151–160 of 353 posts

Re: The Problem with AMP

#151

Post by beezischillin »

mcintyre1994 wrote: post #149

I don't generally disagree with this article but I'd be interested to see research behind "it is a lot easier to stop using the Facebook app or Apple News app than it is to avoid Google search." - for Facebook specifically. I know a few people who view Facebook's app on their phone as the Internet and who would never think to Google search a question. I'd be interested to know how widespread that actually is among Fa…

Make no mistake, Facebook is also about the lock-in. Splitting the main app from Messenger makes a lot of sense in retrospect and is 100% about locking in users and their communication to be within the Facebook platform. Being in a situation where most of your communication goes through one platform, it's absolutely harder to abandon Facebook without abandoning a very important communication tool. Changing a search engine is somewhat easier in my opinion.

Re: The Problem with AMP

#152

Post by saurik »

niftich wrote: post #141
akras14 wrote: post #135

Earlier quoted context omitted.

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:…

Interesting info, but whether or not it's true, it certainly benefits their strategy. I have no doubt that they want to push the narrative that Google (Search) is the 'platform' and the news from publishers they wrap is a tab or viewport that you can [x] (exit) out of, returning to the default 'blank' Google page. The problem with that is that the UX is inconsistent between AMP results and web results. AMP results pr…

Wow: that screenshot makes so much more sense; I wonder why they dropped it... maybe because "back" was confusing with their "swipe left/right to get other articles" hijack?

Re: The Problem with AMP

#153

Post by flukus »

paco3346 wrote: post #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).

Because if it weren't for google forcing AMP on everyone then no one would care about it at all.

Re: The Problem with AMP

#154

Post by sfifs »

lips wrote: post #114
sfifs wrote: post #106

Earlier quoted context omitted.

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

Have you used other compensating mechanisms, like tap-to-show images?

Why should I take the extra effort to make publisher's poor websites usable when something like AMP does it out of the box? I don't really have any ideological objections to Googleplex which would warrant such extra effort.

Re: The Problem with AMP

#155

Post by fortytw2 »

magicalist wrote: post #45
kristianp wrote: post #24

Earlier quoted context omitted.

Can you give an example of how to view reddit via AMP? If I just search for "reddit" on my Android phone for example, there are no AMP links to reddit, only Business Insider etc.

On my phone (chrome on android), basically any google search result from reddit goes to the amp version of the page. (with all five visible comments, and since the full comments are almost certainly what I was searching for, I end up having to click through to the full page anyway every time)

For me, on iOS, I've _never_ had a Reddit AMP page actually finish loading / rendering. Broken since the start

Re: The Problem with AMP

#157

Post by Angostura »

tehlike wrote: post #63
freyir wrote: 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.

Prople in my family get quite confused when trying to share links.

Re: The Problem with AMP

#158

Post by matthewmacleod »

I don't like AMP, and I very glad there is now some push back against Google's implementation of it. Fast pages are great, but I suppose I'm missing the background on why it was necessary to do this, when anybody who can implement AMP could presumably have implemented "lightweight non bloated pages" without using it.

It's bad enough that I've had to switch to using Bing on mobile, despite the worse results, and I'm actually genuinely fearful for the first time about the openness of the web.

Re: The Problem with AMP

#159

Post by pdkl95 »

jshen wrote: post #70
tehlike wrote: 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, "…

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

Well, that explains why they wanted Chrome to hide URLs[1].

[1] https://news.ycombinator.com/item?id=7693995

Re: The Problem with AMP

#160

Post by davedx »

matthewmacleod wrote: post #158

I don't like AMP, and I very glad there is now some push back against Google's implementation of it. Fast pages are great, but I suppose I'm missing the background on why it was necessary to do this, when anybody who can implement AMP could presumably have implemented "lightweight non bloated pages" without using it. It's bad enough that I've had to switch to using Bing on mobile, despite the worse results, and I'm a…

Yeah, I'm tired of not being able to load Reddit from Google SERPs on my phone. Really tired of it.

Time to give DuckDuckGo another try I guess...

Post reply on HN