[millstone]

My specific gripes around AMP as an iPhone user:

1. Scrolling momentum is very different, making it feel non-native

2. The URL bar doesn't hide normally. Scroll down in portrait mode and it doesn't hide.

3. The URL bar doesn't un-hide normally. Switch to landscape mode and scroll up, the URL bar does not reveal itself.

4. Safari Reader mode often doesn't work.

5. Scrolling before the page is done loading can make it look like there's less content then there actually is.

6. Some dynamic sites misbehave (e.g. reddit does not show me as logged in).

7. Copying the URL results in some Google thing instead of the real URL

8. Relationship between AMP X close button and Back button is confusing

I am curious which of these you experience, which you don't notice, and which you don't experience at all if you are an Android user?

[Angostura]

> 7. Copying the URL results in some Google thing instead of the real URL

This is exceptionally annoying, I agree. As a tip though, if you tap the 'sharing' widget, and scroll, you'll see a 'request desktop site' option that will give you the 'proper' URL.

[wanda]

As an iPhone/iOS 10 user, I cannot corroborate all of your claims.

1. Scrolling seems native to me. I just tried it again, maybe it seemed off for a moment. It's hard to tell. I don't find that the scrolling is broken as it is on many websites, and it's not difficult to achieve with -webkit-overflow-scroll: touch in one's CSS, i.e. they could fix this if it's not native already.

2. The URL bar does indeed remain visible. This is normal behaviour when you disable overflow scrolling on the root/body element and enable it on a child element instead. There are a couple of reasons to do this: if you want to size your page relative to the viewport and don't want that size to change when the user scrolls up and down, i.e. you don't want that size to change due to a disappearing/reappearing URL bar, you can force the URL bar to stay visible, thereby forcing a constant height, by doing what I described.

3. This definitely doesn't happen to me.

4. I have yet to encounter an AMP link that didn't work with Safari Reader. I would blame the author of the specific AMP page before blaming AMP as a whole if it works most of the time on other websites.

5. seems like a hazard with most dynamic websites.

6. I cannot say I have experienced, but I do not use Reddit, so maybe that's why.

7. is true. Can't avoid that, regrettably — the whole point of AMP is to serve the site from Google's CDN (and to use AMP components to follow best practices for loading assets). However, I wouldn't call it a disadvantage.

8. I do not find it confusing.

I think 2/3/8 are parts of a bigger and more general problem. The AMP bar simply isn't necessary. It's part of Google's system of control around their AMP pages. AMP should just be an optional way to display pages, there shouldn't be this whole sub-app experience of flicking between AMP articles once an article has been selected from the Google SERP.

It's a nice idea and everything, but what they should have done is implement a similar thing to the Safari reading list, where you're suggested the next article at the bottom of the one you're reading, rather than having an ugly ass navigation bar occupy 10% of the screen.

For one thing, this breaks the gestures for going backwards and forwards in navigation history in iOS Safari, which I would expect to be the first and foremost complaint by any iOS Safari user grappling with AMP.

[euyyn]

> Scrolling momentum is very different, making it feel non-native

Is it different from other web pages, or from scrolling a native app? At the end of the day, an AMP site is HTML.