Jokes on google, AMP sites always crash on my old iphone 4s (the one I use for mindless browsing), so I just avoid AMP content
Kill Google AMP before it kills the web
281–290 of 489 posts
Re: Kill Google AMP before it kills the web
#282With respect to scrolling: We (AMP team) filed a bug with Apple about that (we didn't implement scrolling ourselves, just use a div with overflow). We asked to make the scroll inertia for that case the same as the normal scrolling. Apple's response was (surprisingly) to make the default scrolling like the overflow scrolling. So, with the next Safari release all pages will scroll like AMP pages. Hope Gruber is happy t…
Wouldn't this line of CSS: -webkit-overflow-scrolling: touch; have addressed the issue?
That line causes the observed behavior. But it improves it over not being present.
Re: Kill Google AMP before it kills the web
#283What's going to be interesting is if browsers can at some point render a APM version of a page natively. What I mean is render the original page on the source website as APM content. That will stop the monopoly and hijacking (or rather the rationalization of it) of target websites in Google results.
Re: Kill Google AMP before it kills the web
#284What kills me about AMP's UX is that not only is it a dark pattern, it's not even a new dark pattern.
Back, say, 10-12 years ago it used to be really common for sites to jigger their outgoing links, such that the target site would appear in an iframe underneath a toolbar from the original site. This was widely reviled, and mostly died out, and the fact that Google is reviving it really bothers me.
Re: Kill Google AMP before it kills the web
#285What's going to be interesting is if browsers can at some point render a APM version of a page natively. What I mean is render the original page on the source website as APM content. That will stop the monopoly and hijacking (or rather the rationalization of it) of target websites in Google results.
Or as a start, maybe a browser extension/plugin where it renders it for certain configured sites.
Re: Kill Google AMP before it kills the web
#286As a user, I love AMP. Pages load fast, and that's about all I really care about.
I don't really do web dev anymore, but if I was I think I'd be happy about using it.
Maybe a content creator feels differently but I don't have any experience with that.
Re: Kill Google AMP before it kills the web
#287AMP needs to either be drastically rethought or killed. Nothing more annoying for me on my iPhone than clicking a link and it's AMP - as it means missing features, broken scrolling, masked URL and worst of all, in page search is totally broken on the iPhone! So annoying that there is no way to disable it - if Google persist in pushing it then it might push me to try alternatives!
Google's broken AMP crap is what made me switch to duckduckgo on iOS.
It seems to me that only iOS users are complaining -- as an Android user I am blown away by how readable AMP pages are.
I can just get to the page, read it, and then leave. There's no futzing around with:
* long scrolling down "the fold" filled with clickbait in-site links or other unrelated nonsense
* interstitial and overlay ads
* crappy non-mobile interfaces
* "Shared" buttons stickied to the bottom or top of the viewframe
There's still ads around the page (in-content ads between paragraphs and "you may like" or "recommended" ads at the bottom of the page) and navigational elements to browse outside of the AMP page. It's the mobile content consumption experience as it should be.
Re: Kill Google AMP before it kills the web
#288AMP needs to either be drastically rethought or killed. Nothing more annoying for me on my iPhone than clicking a link and it's AMP - as it means missing features, broken scrolling, masked URL and worst of all, in page search is totally broken on the iPhone! So annoying that there is no way to disable it - if Google persist in pushing it then it might push me to try alternatives!
A way to disable it while seeing Google results is to start from DuckDuckGo but add "g!". This goes through a different Google interface that always returns normal links.
Re: Kill Google AMP before it kills the web
#289AMP needs to either be drastically rethought or killed. Nothing more annoying for me on my iPhone than clicking a link and it's AMP - as it means missing features, broken scrolling, masked URL and worst of all, in page search is totally broken on the iPhone! So annoying that there is no way to disable it - if Google persist in pushing it then it might push me to try alternatives!
A way to disable it while seeing Google results is to start from DuckDuckGo but add "g!". This goes through a different Google interface that always returns normal links.
I believe you mean "!g". DuckDuckGo "macros" start with bang.
Re: Kill Google AMP before it kills the web
#290What kills me about AMP's UX is that not only is it a dark pattern, it's not even a new dark pattern. Back, say, 10-12 years ago it used to be really common for sites to jigger their outgoing links, such that the target site would appear in an iframe underneath a toolbar from the original site. This was widely reviled, and mostly died out, and the fact that Google is reviving it really bothers me.
How is this a dark pattern? Sites opt into it, users get a streamlined interface for content consumption, everybody wins.
The only losers in this are those seeking to "curate" the user experience (UX) on their sites, and personally I lump them in with malicious ad peddlers -- to hell with them.