1. 12

    I think of Material Design more of a safety net. We can’t expect every app maker to be proficient in design and creating something interesting, unique, and useful. MD saves the average app developer from making a really really terrible app. Yes, you still have to understand the design philosophy, the guidelines, the patterns. But it’s easier to use a set of components Google has made for you and copy patterns that occur in the MD-complaint apps.

    Disclaimer: I work at the GOOG.

    1. 8

      As a backend developer that has had to take on the lead on a few front end projects, this is a massive win. You can simply follow material design spec and get solving problems, then when someone queries why you have done something or wants something changed, you can just quote the material spec and get on with solving real problems.

      1. 7

        “real problems”

        1. 3

          and get on with solving real problems.

          I think if the application in question is small enough, then this might hold true; however once the project gains any significant complexity or scope then I’d say having a backend developer work on UI might cause a few ‘real problems’ of its own ;)

          1. 3

            This an example of the kind of conclusion you don’t want to jump to. Material Design may be a good stand-in, but it is ultimately a one-size-fits-all solution to a problem (yes, a real one 😉) that is inherently case-by-case. It helps developers speed through UI design; it does not solve UI design. As much as Google may want you to believe that convenient untruth.