The flip side is that interfaces have tended too much towards faux 3d on a superflat 2d screen and also ignoring that the UI can be "authentically digital" instead of being tied down to analog equivalents. I find the author's analysis very simplistic.
Also, this is just about mostly about the buttons and links which can probably be fixed easily in the future. Metro is much much more than that, Metro also removes a lot of unnecessary chrome like lines around menus etc. and reducing visual clutter which are very important on mobile devices where you're looking for actual information in a pinch on-the-go. The codeword for this is "Content over Chrome".
Anyone see the similarities between this[1] from 20 years ago and the iPhone UI + every other mobile OS including Android, Palm, Windows Mobile < 7, Blackberry, Meego, Firefox OS etc.?
Here's more information if you're interested in the design philosophy behind Metro written by an actual designer who designed Metro like content for his clients' websites.
Hopefully all this results in better UIs in the future instead of the tired old jaded WIMP interface and Desktop on mobile yet again with some added touch features and I think Microsoft has taken a good first step here to shake things up.
I don't know how Metro looks lately, but when I tested a WinMo 7, the interface gave no clues of what elements are clickable and what elements aren't. So I ended up clicking like an idiot on images and on text, which sometimes triggered a click and sometimes it didn't, depending on how static or not the element was.
You can see this mistake in some Android/iOS apps that come with their own custom designs. For instance Twitter on iOS is friendly and all, but after expanding a tweet, to view the full profile of that user, you have to click on that profile's image, while the profile's name is NOT clickable. I always make the effort of going through "what the hell do I click on? every single time I want to view a profile.
So if this still happens in Metro, with the UI giving no visual clues as to what elements can be touched/clicked or not, then your argument is not really valid, being a poor rationalization. In the real world things that can be acted upon either provide audio, visual or tactile clues (or all of them at once).
Also, I agree that the design in Android Jelly Bean tends towards the same kind of flat look. It looks indeed nicer, but it's not as radical. In general, buttons are still buttons, with the exception of things that are designed to be clicked as an after-thought (e.g. the clock widget's primary function is showing the clock, but it opens the dialog for setting an alarm if you touch it, but that's not the only way of setting an alarm, being just a convenient shortcut). There are some annoyances too, like the phone pad for dialing numbers, which just shows some white numbers on a dark background, something that's annoying me greatly.
Looking at the link http://www.riagenic.com/archives/487 it shows they contrasted Metro with gaudy and awful chrome. I think it is a bit of a straw man in this case. Metro just took a idea and implemented the extreme of it. And extremes don't always work well there needs to be some compromise. This doesn't have to be all 0 or all 1 (all gaudy horrible chrome or completely flat polygons filled with color).
"authentically digital" -- I am all for it except that most people already have some baggage or notions of how interfaces work (both in real world and digital). It also happens that those in digital world mimic those in the real world (buttons have shadows for ex) or some conventions have stuck that have been randomly chosen initially (links are underlined).
Now maybe it is a noble goal to re-educate the user and I can see that. I remember hating Ubuntu's Unity. Now I like. It has re-educated me. But I also happened to like other aspects of Ubuntu and didn't want to switch to an alternative that why I stuck with it. But it seems a lot of people did and a lot of people will also do that to Windows.
Also, this is just about mostly about the buttons and links which can probably be fixed easily in the future. Metro is much much more than that, Metro also removes a lot of unnecessary chrome like lines around menus etc. and reducing visual clutter which are very important on mobile devices where you're looking for actual information in a pinch on-the-go. The codeword for this is "Content over Chrome".
Android(starting with ICS) also is trending a bit towards Metro in things like the weather app, Google Now and the overall designed aesthetic. https://lh4.ggpht.com/p-eZmyce7_T2-_eOwltQxU6glPj6f53kDXvDvN...
Anyone see the similarities between this[1] from 20 years ago and the iPhone UI + every other mobile OS including Android, Palm, Windows Mobile < 7, Blackberry, Meego, Firefox OS etc.?
[1] http://img.tfd.com/cde/_PROGMAN.GIF
Here's more information if you're interested in the design philosophy behind Metro written by an actual designer who designed Metro like content for his clients' websites.
The principles of Microsoft Metro UI decoded http://www.riagenic.com/archives/487
Going full Metro. http://www.riagenic.com/archives/493
Things you ought to know when designing metro screens http://www.riagenic.com/archives/526
Hopefully all this results in better UIs in the future instead of the tired old jaded WIMP interface and Desktop on mobile yet again with some added touch features and I think Microsoft has taken a good first step here to shake things up.