101–110 of 489 posts
I agree 100% with his frustration with AMP scrolling behavior on iOS.
On a more serious note it is extremely frustrating. Everything about the AMP UX on iOS is broken.
Earlier quoted context omitted.
The fact that you say android explains everything to me. I'm sure Google made sure it was a decent experience on their operating system. But it's clear they didn't give two seconds thought to iOS, and haven't bothered to improve it since it was released. It really does make google search feel broken. Many of the top results no longer "work right". Ignoring all the other issues of who is in control and whether it's a…
Well now you know how most of those web pages felt on Android before - web devs tested on mobile Safari and left pages broken and utterly stuttery on Android web browser.
Earlier quoted context omitted.
Well, it is Gruber we are talking about. He believes in openness when it suits Apple - AMP outputs standard HTML5 which Safari renders - it does its own scrolling but he doesn't quite like it. Google doesn't 'respect' that closed platform. On that 'crime' Gruber has this to say - "If I had my way, Mobile Safari would refuse to render AMP pages." You might have valid reasons not to use AMP but Gruber's are merely that…
AMP does NOT outperform HTML5 unless the HTML5 page is horribly designed and ridiculously bloated. But that can be fixed without Google's help. I'm not sure why your dismissive of the scrolling thing. Having something breaks the feel of the web browser is a really bad idea. Additionally he's completely right that it breaks other platform conventions that users expect to use. You can't use the share button, you can't…
AMP webpages are fast and responsive. Publishers that don't use AMP now have to make their webpages fast. Competition is good for the user and the web.
Earlier quoted context omitted.
Well now you know how most of those web pages felt on Android before - web devs tested on mobile Safari and left pages broken and utterly stuttery on Android web browser.
That's because Chrome on Android sucked.
Earlier quoted context omitted.
AMP does NOT outperform HTML5 unless the HTML5 page is horribly designed and ridiculously bloated. But that can be fixed without Google's help. I'm not sure why your dismissive of the scrolling thing. Having something breaks the feel of the web browser is a really bad idea. Additionally he's completely right that it breaks other platform conventions that users expect to use. You can't use the share button, you can't…
I have to admit, I've been on iOS for years and only ever use Safari for browsing, and NEVER had I heard about this tap the top bar to scroll to the top behavior.
"If you don't like the news, go out and make some of your own." Is anyone working on a competing standard?
It's called HTML, and it's been around for a number of years. If you don't put 12 megs of JavaScript on it and five auto playing video ads… you'd be surprised how fast web pages can be. This isn't a problem that "needs" solving. It's not like it's impossible or even difficult to make a fast loading pages with the existing technologies. The people who didn't care before or just outsourcing it to someone else who doesn…
In theory, someone else could create another standard and write browser extensions to put an icon on links that meet that standard.
The HTML standard doesn't help with this, not by itself, anyway.
Earlier quoted context omitted.
Well, it is Gruber we are talking about. He believes in openness when it suits Apple - AMP outputs standard HTML5 which Safari renders - it does its own scrolling but he doesn't quite like it. Google doesn't 'respect' that closed platform. On that 'crime' Gruber has this to say - "If I had my way, Mobile Safari would refuse to render AMP pages." You might have valid reasons not to use AMP but Gruber's are merely that…
AMP does NOT outperform HTML5 unless the HTML5 page is horribly designed and ridiculously bloated. But that can be fixed without Google's help. I'm not sure why your dismissive of the scrolling thing. Having something breaks the feel of the web browser is a really bad idea. Additionally he's completely right that it breaks other platform conventions that users expect to use. You can't use the share button, you can't…
Earlier quoted context omitted.
AMP does NOT outperform HTML5 unless the HTML5 page is horribly designed and ridiculously bloated. But that can be fixed without Google's help. I'm not sure why your dismissive of the scrolling thing. Having something breaks the feel of the web browser is a really bad idea. Additionally he's completely right that it breaks other platform conventions that users expect to use. You can't use the share button, you can't…
I have to admit, I've been on iOS for years and only ever use Safari for browsing, and NEVER had I heard about this tap the top bar to scroll to the top behavior.