6 ms·

I hope the next step is a way to strip AMP links from all URLs, backfilling the "Disable AMP" setting that Google ought to have provided. AMP has always worked

I hope the next step is a way to strip AMP links from all URLs, backfilling the "Disable AMP" setting that Google ought to have provided. AMP has always worked poorly on iOS: it has different scrolling, it breaks reader mode, and it breaks status bar autohide and jump-to-top. Perhaps Apple would be less hostile to AMP if the implementation were better.

ashark 9y ago
It also breaks "back" IIRC. They expect you to use the "x" on the page to navigate back, not.. you know, the back button built into the browser. That and the scrolling are what got me to switch my iphone to DDG.
- droopybuns 9y ago
  It also breaks saving URLs in evernote mobile! Down with AMP!
- PerryCox 9y ago
  Not breaking the back button should be #1 on every webpages priority list. If you break my back button I can almost guarantee I will stop using your site because in my mind the only sites that do that are spam/scams.
- zeitg3ist 9y ago
  This is a general Google trend it seems. Google Images does it too: if you scroll left after viewing an image, you get the previous result instead of the page you were on. Really frustrating.
  - nneonneo 9y ago
    Google blogs do this as well, showing you the "previous" blog post when you swipe left. Again, massive usability issue. I don't understand why Google has to break these well-established UI conventions.
    - zeitg3ist 9y ago
      Don't even get me started about this Blogger thing. The triggers are so sensitive that half the time I switch articles when I'm just trying to scroll down.
  - stephen_g 9y ago
    Ah, yes, that is incredibly annoying behaviour. I was getting annoyed at this just yesterday! That would be fine on iOS if it only happened when you flicked the image, but scrolling from the side edges of the screen in Safari should always navigate forward and back. They must have actually had to do work to override the expected behaviour and break the user experience, which I just don't get.
- seanp2k2 9y ago
  Maybe they can put it as a big round button in the bottom-right so it doesn't break with Material Design too.
- cormacrelf 9y ago
  Is it just my memory or do you have to manually thumb your way to the top of a very long page in order to press said X button?
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 ago
  Don'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 ago
    I thought the point of AMP was to force ads, by stopping ad blockers from working.
- e1ven 9y ago
  A 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 ago
    This 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.
ajmurmann 9y ago
It also frequently crashes the browser when zooming in on something on the page.
madeofpalk 9y ago
> it has different scrolling Actually, AMP pages had the most consistent scrolling with the rest of the system. It was 'regular' web pages that had the different scrolling iOS 11 fixes that. All pages now scroll at the same 'speed' as the rest of the system.

ashark 9y ago

It also breaks "back" IIRC. They expect you to use the "x" on the page to navigate back, not.. you know, the back button built into the browser. That and the scrolling are what got me to switch my iphone to DDG.

droopybuns 9y ago
It also breaks saving URLs in evernote mobile! Down with AMP!
PerryCox 9y ago
Not breaking the back button should be #1 on every webpages priority list. If you break my back button I can almost guarantee I will stop using your site because in my mind the only sites that do that are spam/scams.
zeitg3ist 9y ago
This is a general Google trend it seems. Google Images does it too: if you scroll left after viewing an image, you get the previous result instead of the page you were on. Really frustrating.
- nneonneo 9y ago
  Google blogs do this as well, showing you the "previous" blog post when you swipe left. Again, massive usability issue. I don't understand why Google has to break these well-established UI conventions.
  - zeitg3ist 9y ago
    Don't even get me started about this Blogger thing. The triggers are so sensitive that half the time I switch articles when I'm just trying to scroll down.
- stephen_g 9y ago
  Ah, yes, that is incredibly annoying behaviour. I was getting annoyed at this just yesterday! That would be fine on iOS if it only happened when you flicked the image, but scrolling from the side edges of the screen in Safari should always navigate forward and back. They must have actually had to do work to override the expected behaviour and break the user experience, which I just don't get.
seanp2k2 9y ago
Maybe they can put it as a big round button in the bottom-right so it doesn't break with Material Design too.
cormacrelf 9y ago
Is it just my memory or do you have to manually thumb your way to the top of a very long page in order to press said X button?

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 ago
Don'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 ago
  I thought the point of AMP was to force ads, by stopping ad blockers from working.
e1ven 9y ago
A 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 ago
  This 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.

ajmurmann 9y ago

It also frequently crashes the browser when zooming in on something on the page.

madeofpalk 9y ago

> it has different scrolling Actually, AMP pages had the most consistent scrolling with the rest of the system. It was 'regular' web pages that had the different scrolling iOS 11 fixes that. All pages now scroll at the same 'speed' as the rest of the system.