Lovely detailed article! Looking forward to seeing more of these :)
"Simply put, both sides are “right”, because both app teams need to uphold the principles set forth by their platform teams. Apple Maps would look wrong if it embraced Material, despite the 7% gain in real estate, and Google Maps wouldn’t feel “Google-like” if it embraced a pure iOS design. They’re both doing exactly the right thing here."
I don't agree with this part of the article though. They're comparing both Google and Apple maps on the iOS8 platform. In my opinion, doing "exactly the right thing" would be to stick with guidelines of the platform you're building for. In the case of Google I get why they stick to Material, but I don't agree that it's the best thing to do.
Hi Rick! Glad you liked the article. Thanks!
I totally agree that any one of my assertions have tradeoffs. And personally I'm the most "stick with the platform" designer I know. So I agree with you 100% percent philosophically.
But in my experience it's just not feasible to tell a Microsoft, or a Facebook, or a Google to default to the conventions of the platform rather than the conventions of the company. Respecting the platform is always my strategy on the teams I'm on, but the tactics are tricky. It ends up being hand-to-hand combat on each issue rather than declaring a sweeping philosophy up front and assuming everyone will fall into line.
Though I wish that worked for me. It'd save a lot of time :)