5 ms·
AMP has always worked poorly on iOS... This never made sense to me. You can have natural scrolling, an accurate reader view, a working back button and other h
by pdog 9y ago
AMP has always worked poorly on iOS...
This never made sense to me.
You can have natural scrolling, an accurate reader view, a working back button and other highly performant features in a mobile-optimized HTML and CSS standard like AMP. In fact, you practically have to go out of your way to break these things in the way that AMP does.
Why does AMP have to suck so much?
- seanp2k2 9y agoDon't forget that many pages won't even load if you have some adblockers loaded. My typical usage also requires a "reload without content blockers" to get anything at all to show up on AMP pages. Crazy idea, I know, but maybe Google could provide even a way to get to a non-AMP version from a SERP. Even better, let me disable AMP completely, but forcing it on everyone like this and refusing to back down just shows how they value their users, AKA their sources of revenue.
- eulevik 9y agoI thought the point of AMP was to force ads, by stopping ad blockers from working.
- e1ven 9y agoA significant portion of the time (more than 1/2) AMP URLs fail to load, forcing me to "Request Desktop Site" in order to load it. When they do load, they fuckify the URL, so I can't copy/paste it normally. I know I can go in through the page's menus and get the real URL, but it makes it harder for no reason. I consider the URL part of the page's UI, and commonly manually edit it. This makes it harder. So far as I can see, there is no advantage to AMP pages, versus a fast and simple HTML page, with no external resource requests. Sites can serve that themselves, rather than using Google. In short, it breaks features I use, and doesn't provide advantages.
- BoorishBears 9y agoThis is why I hate AMP. People who like it can't seem to understand that it has a crappy user experience for some people and always assume you don't like it for "philosophical reasons". I really don't care about AMP from that POV, I just wish it was a secondary link instead of the stealth replacement of where I wanted to go with a page that usually doesn't load and messes up my back button.
- protomyth 9y agoI’m with you. I expect in the coming days I will have to switch some of our elder’s search engines to DuckDuckGo to avoid problems. I just hate technology that changes the user experience in a broken way. Browsers are supposed to act in a certain way. Don’t break that. Breaking UI is why we had a hate on for Win 8. It really annoyed people with the changes.
- ethnic_throw 9y ago> You can have natural scrolling, an accurate reader view, a working back button and other highly performant features in a mobile-optimized HTML and CSS standard like AMP. In fact, you practically have to go out of your way to break these things in the way that AMP does. > Why does AMP have to suck so much? Because it violates every assumption on how browsers should work. I would prefer a slow browser I understand to a fast one I can't control.
- lucaspiller 9y agoI'm not sure if it has changed recently, but I just tried it and the browser back button is working fine (it goes back to the search results). My only real complaint about AMP is the scrolling - it doesn't feel natural and breaks shrinking the browser UI (I have an iPhone 5S, so screen real-estate is a premium).
- ec109685 9y agoNatural scrolling comes to safari in iOS 11, so every site will behave like amp.
- ancarda 9y agoDo you have a source with more information? Because that will drive me so mad I won't update iOS if it's true.
- ec109685 9y agohttps://www.google.com/amp/s/www.macrumors.com/2017/05/22/scrolling-changes-coming-to-mobile-safari/amp/ https://www.google.com/amp/s/www.macrumors.com/2017/05/22/sc...