3 ms·

Please explain why you hate it?

teraflop 9y ago
Most of the time I don't care one way or another. Occasionally I search Google for Reddit posts on my phone, and it's mildly infuriating to get a bunch of AMP results, because I strongly prefer the desktop UI that I've chosen in my preferences over the default mobile UI that AMP shows.
peterwwillis 9y ago
It actually breaks pages. Not only their functionality but the browser will actually close the page or go back to the search results with amp, and sometimes clicks don't work. It also loads "weird". I almost always have to furiously click the 'link' icon on top to load the real page, because the page was designed to load under real-world conditions, not through a web proxy. Aside: from a privacy perspective it creeped me the hell out once I realized what was happening.
j79 9y ago
Not OP, but the primary issues I'm not a fan (on iOS) are: 1) Performance - Yes, it LOADS fast, but MANY pages "feel" janky, when scrolling, especially pages that allow you to load additional accords by scrolling left/right. Only the simplest pages don't "jank" on my device. 2) Scrolling - It isn't the native scroll. It seems to be a div with "overflow-scrolling" applied. Other than that feeling "off", it prevents the bottom toolbar from hiding, reducing screen real estate. 3) Sharing URLs. 4) Biggest: No way to opt-out. I'm a fan of the open web. It's why I prefer a website to a sandboxed experience you get with native apps. At least for the first click on Google SERP pages, I'm "stuck" with google.com. One note: I get the AMP use case, and I'm sure there are users who prefer AMP pages for the performance they see. However, I'm fortunate enough to live in an area with decent mobile speed/bandwidth, and loading the original pages are rarely "slow" on my device. However, the originals all address the issues I noted above. I'll take the .5-1 second delay for the original(s), over the AMP version.
- dormento 9y ago
  You can try going to https://encrypted.google.com https://encrypted.google.com, it seems to not show amp-crippled content.
Aaargh20318 9y ago
Because I want the full web experience, not some neutered version. I’ve been in mobile development for about a decade, what Google did was re-invent WAP on top of HTML5, turning back the clock at least 10 years.
- peterwwillis 9y ago
  Google has become an OSP. All they need to do is start using their monopoly on ccTLDs to create dark web google services that you can only get to via Google internet connections. If they switched their core services over to that, they could require you use a Google tunnel to use their services. By also sending all non-Google traffic through the tunnel ("for improved speed!" remember when AOL included SpeedBooster Technology?) they'd control a majority of all non-search internet traffic, like AOL without the disks. And they wouldn't even have to bill you because they'd get an unlimited supply of ad data.
isleyaardvark 9y ago
1) Scrolling is broken. 2) Touching tap to return to the top of a webpage is broken. 3) Searching for a word within a webpage is broken. This is all basic functionality that I use often. And I'm sure there are other things broken about it.

Most of the time I don't care one way or another. Occasionally I search Google for Reddit posts on my phone, and it's mildly infuriating to get a bunch of AMP results, because I strongly prefer the desktop UI that I've chosen in my preferences over the default mobile UI that AMP shows.

peterwwillis 9y ago

It actually breaks pages. Not only their functionality but the browser will actually close the page or go back to the search results with amp, and sometimes clicks don't work. It also loads "weird". I almost always have to furiously click the 'link' icon on top to load the real page, because the page was designed to load under real-world conditions, not through a web proxy. Aside: from a privacy perspective it creeped me the hell out once I realized what was happening.

j79 9y ago

Not OP, but the primary issues I'm not a fan (on iOS) are: 1) Performance - Yes, it LOADS fast, but MANY pages "feel" janky, when scrolling, especially pages that allow you to load additional accords by scrolling left/right. Only the simplest pages don't "jank" on my device. 2) Scrolling - It isn't the native scroll. It seems to be a div with "overflow-scrolling" applied. Other than that feeling "off", it prevents the bottom toolbar from hiding, reducing screen real estate. 3) Sharing URLs. 4) Biggest: No way to opt-out. I'm a fan of the open web. It's why I prefer a website to a sandboxed experience you get with native apps. At least for the first click on Google SERP pages, I'm "stuck" with google.com. One note: I get the AMP use case, and I'm sure there are users who prefer AMP pages for the performance they see. However, I'm fortunate enough to live in an area with decent mobile speed/bandwidth, and loading the original pages are rarely "slow" on my device. However, the originals all address the issues I noted above. I'll take the .5-1 second delay for the original(s), over the AMP version.

dormento 9y ago
You can try going to https://encrypted.google.com https://encrypted.google.com, it seems to not show amp-crippled content.

Aaargh20318 9y ago

Because I want the full web experience, not some neutered version. I’ve been in mobile development for about a decade, what Google did was re-invent WAP on top of HTML5, turning back the clock at least 10 years.

peterwwillis 9y ago
Google has become an OSP. All they need to do is start using their monopoly on ccTLDs to create dark web google services that you can only get to via Google internet connections. If they switched their core services over to that, they could require you use a Google tunnel to use their services. By also sending all non-Google traffic through the tunnel ("for improved speed!" remember when AOL included SpeedBooster Technology?) they'd control a majority of all non-search internet traffic, like AOL without the disks. And they wouldn't even have to bill you because they'd get an unlimited supply of ad data.

isleyaardvark 9y ago

1) Scrolling is broken. 2) Touching tap to return to the top of a webpage is broken. 3) Searching for a word within a webpage is broken. This is all basic functionality that I use often. And I'm sure there are other things broken about it.