JoshMnem
Joined 13 years ago
Joined 13 years ago
One problem is that Google wants AMP to replace HTML. I've already seen AMP pages in the Google search results (on desktop), and at least one large website so far appears to be built entirely in AMP.[1]
Google already sends desktop users to Wikipedia's mobile site from some of their listings, so I wouldn't be surprised if Google eventually starts to send desktop users to AMP pages. Google benefits when people visit AMP sites, because Google will be able to spoof the domains and serve the content themselves, giving them increased control over publishers.
[1] independent.co.uk, but they removed the CSS that delays page loading.
Some people don't want to load resources from Google's servers, and they shouldn't be punished for it. That JS file isn't needed for AMP pages to load. People don't need to load JS to read text and view images. I don't think there is any reasonable argument to have any users hit an 8-second delay.
https://www.cnet.com/news/google-is-tracking-your-purchases-...
A company shouldn't design its website with Google or Apple's visual branding as if it were locked into a closed platform. It also appears to be a problem with things like Flutter, though I haven't looked closely.
There's a battle between some of the large tech companies for appification of the Web at the moment, and that way of thinking is a trap.
Sorry to disagree, but Material Design itself lacks aesthetic restraint and has accessibility problems with the constant flashing and animation, but that's another conversation.
Edit: I'm talking about the browser, not apps (though I don't like MD there either). I mean that websites shouldn't change their design based on the company that makes the web browser.
Having that as a default means that many people will implement it.