|
Software is made of a set of symbols unique to its particular function, and user interaction at its most primitive is no more than the relationship of those symbols to the ones present in the mind of the user. The latest fads in user interaction design seem to ignore this perspective, and instead treat "UI" as another abstraction layer of unique symbols on top of software, then expecting all software to be designed top-down based off this "unified design language". This approach unfortunately ignores the user, providing further indirection away from the underlying software and it's function, herding the user into a church of the designer's own construction where they are now forced to worship interaction in the abstract as a prerequisite to using the software (or at least blindly perform whatever rituals it demands). The aim of design unification is often a false path, born out of convenience for the designer, and it's pursuit shows a certain level of disrespect to both the user and other designers. Programming languages - arguably interaction design in its purest form - are a more interesting path towards better software (see Smalltalk, Swift playgrounds, and the work at VPRI). Material is not what software is made of, but it is a pretty good sign of what marketing is made of these days. |
Of course it's marketing; they're doing a huge marketing push on this. Even writing "Material" makes me feel like I'm helping some marketing team somewhere.
But saying that this is made up out of whole cloth completely ignores the fact that not only does it engage with the existing design language of other mobile platforms, it also flows quite nicely from "holo" and cards from previous Android versions. Moreover, it's fairly loose as design guidelines go, providing recommendations but not forcing you into a particular unified design.
The designer in that article from yesterday got it quite right: this is post-rationalization, taking what already existed and trying to find the unifying aspects of what gave clarity and discarding what was confusing. That is not the same thing as a dictated UI.
Your response is generic and could be copy-pasted on any article claiming to be about common aspects of a design language. This is exactly why it's voted up (and why it fits "middle-brow" to the t), because if you actually brought up any actual specifics about the article or "Material" it would be immediately obvious that claims of ignoring a relationship with what the user knows or with how the software is actually written are overblown and theatrical.