Interesting thread, via @iOSDevWeekly, about Google deciding to deprecate its iOS Material Components libraries.

Platform-appropriate design is easier to use for both developers and users, it turns out! https://t.co/3aoP73RQSy

— Ellen Shapiro (@designatednerd) October 8, 2021

Google probably not helping here, but I do wish Apple would do it ... https://t.co/5FTtDDKuTa

— benlovejoy (@benlovejoy) October 8, 2021

Fun fact: when I was working on the iCloud web apps we had to redraw all of the super detailed iPad UI from scratch because there was no sharing of design source files between teams at Apple.

The Calendar / Contacts UI were styled after planner books. So many photoshop layers… https://t.co/gzzdntrEtD pic.twitter.com/6H5eUXYqZW

— Sebastiaan de With (@sdw) October 8, 2021

Google apps using material design on iOS is an example of confusing a business problem with a people problem. Users care about all the apps on their phone behaving similarly. Google apps behaving like Android apps was great for corporate synergy not users.https://t.co/O2hzGF1lsj

— Dare Obasanjo (@Carnage4Life) October 9, 2021

The time we're saving not building custom code is now invested in the long tail of UX details that really make products feel great on Apple platforms. To paraphrase Lucas Pope, we're "swimming in a sea of minor things", and I couldn't be more excited about this new direction.

— Jeff Verkoeyen (@featherless) October 7, 2021

This is part of why the public MDC repo is in maintenance mode. With the introduction of SwiftUI and significant UIKit improvements in iOS 14+, it's never been easier to build a great branded experience with a tiny amount of code.

And the best code is often no code :)

— Jeff Verkoeyen (@featherless) October 7, 2021

This is big news for iOS users frustrated with the performance and behaviors of Google’s apps on the platform. https://t.co/4AnSZE7W4y

— Tim Holmes (@tpoholmes) October 8, 2021

This is so important. The same goes for apps who build a custom UI across platforms. Apps should have a common design paradigm with the platform they’re on. Users don’t care about your brand, or wherever the reason.

’Google’s apps to embrace iOS on iOS’ https://t.co/RQAuOIQorL

— Max Rudberg (@maxrudberg) October 9, 2021

Since 2012 and the original launch of Google Maps iOS, my team has supported the creation and maintenance of shared UI components across Google. This was originally born out of a need to fill gaps in UIKit's design language.https://t.co/1GIntCmQMT

— Jeff Verkoeyen (@featherless) October 7, 2021

I literally remember asking a designer for an asset, and they asked me to leave their desk because they had to pull it from a secret folder I couldn’t know about

— Majd Taby (@jtaby) October 8, 2021

Fascinating. Google’s 10 year journey to create great mobile apps, leading to creation of Material UI framework, and now leading to embracing native iOS UI elements. https://t.co/vCkdqyYPIO

— Gene Kim (@RealGeneKim) October 9, 2021

I think the TL;DR of this thread is that Google apps on iOS will start looking like they were born on iOS in future, rather than looking like they’re from another planet. https://t.co/Zl0bx6OpLU

— Charles Arthur (@charlesarthur) October 8, 2021

Either way I'm glad for them to be doing it. It sounds like Google's iOS apps are about to get a whole lot better ?

— Collin Donnell (@collindonnell) October 8, 2021

My last job at Apple was rebuilding https://t.co/mNKaXLF7xa to use the iPad interface on the desktop web.

My soul died when I replaced the native drop down with an iPad-style popover.

Still haven’t emotionally recovered from that https://t.co/EMs3jfmwB6

— Majd Taby (@jtaby) October 8, 2021

After ~10 years, Google is winding down its Material Design custom UI work on iOS in favor of pure UIKit. Why? UIKit got better, and “time we're saving not building custom code is now invested in the long tail of UX details that really make products feel great on Apple platforms” https://t.co/bkXn9ZmyGm

— Steve Troughton-Smith (@stroughtonsmith) October 8, 2021

Along the way, the problems we aimed to solve grew from filling gaps in UIKit to bridging design language gaps across platforms. Material came into being, and we eventually sourced many of our libraries as Material Components for iOS (MDC).https://t.co/F79IUjHso6

— Jeff Verkoeyen (@featherless) October 7, 2021

I’ve never liked Google’s iOS for not adhering to Apple’s UI conventions. As a heavy Nest user, it’s one reason I cling to the OG Nest app rather than Google Home for our cameras. https://t.co/IZaiCMRSTm

— Steven Aquino (he/him) (@steven_aquino) October 8, 2021

I'm trying to understand what was missing in UIKit for the past 10+ years which necessitated creating their entire own UI toolkit in the first place when it worked for every other app on the platform. What was wrong with a UISwitch or UITableView five years ago but is okay now?

— Collin Donnell (@collindonnell) October 8, 2021

Apple goes with RCS right after they migrate iMessage to Android. https://t.co/UI31NxysAa

via @GoogleNews

— Michael Gartenberg (@Gartenberg) October 8, 2021

This evolution of how we approach design for Apple platforms has enabled us to marry the best of UIKit with the highlights of Google's design language.

The result? Many custom components simply aren't needed anymore. And the ones that are, they now get more attention and focus.

— Jeff Verkoeyen (@featherless) October 7, 2021

It's now been almost ten years now since we set out on this journey, and many of the gaps MDC had filled have since been filled by UIKit — often in ways that result in much tighter integrations with the OS than what we can reasonably achieve via custom solutions.

— Jeff Verkoeyen (@featherless) October 7, 2021

GoogleがiOS向けに提供していた公式のMaterial Designライブラリをメンテモードに移行したとのこと。
理由は、UIKitが年々アップデートされていってMDライブラリでわざわざカスタマイズする必要性が減り、更にUIコンポーネントを独自実装することにより生じる副作用が無視できなくなってきた等。 https://t.co/M5rpjVo6SO

— usagimaru ⌘ (@usagimaruma) October 8, 2021

Fascinating. Google’s 10 year journey to create great mobile apps, leading to creation of Material UI framework, and now leading to embracing native iOS UI elements. https://t.co/vCkdqyYPIO

— Gene Kim (@RealGeneKim) October 9, 2021

Excited to see what this looks like but reverting to Apple’s design language always seemed inevitable.

A bunch of people got promoted for creating Material design and now new people can get promoted for undoing Material design. Is that too cynical? https://t.co/TnCG4SZ0oc

— Chris Lewis  (@chrislewis_aus) October 9, 2021

Interesting thread and highlights again the value in having access to and using the native UI capabilities on each mobile platform. https://t.co/ykPJSKlO6H

— John O'Reilly (@joreilly) October 8, 2021

Google apps using material design on iOS is an example of confusing a business problem with a people problem. Users care about all the apps on their phone behaving similarly. Google apps behaving like Android apps was great for corporate synergy not users.https://t.co/O2hzGF1lsj

— Dare Obasanjo (@Carnage4Life) October 9, 2021

구글 개발자, 트윗 스레드로 더 이상 구글 Material 디자인을 iOS에 포팅하지 않고 자체 인터페이스 사용할 예정이라 언급. UIKit이 충분히 진화해 더 이상 '빈틈'을 메울 필요가 없기 때문이라 설명했지만, 일각에서는 애초에 그런 간극이 있었는지 의문을 제기하기도. https://t.co/GthsJlnvSk

— Paranal (@nagato708) October 8, 2021

구글은 그 동안 iOS용 구글 앱들에 자사의 Material Design UI을 적용해 왔으나, 올해부터 이를 포기하고 iOS 표준 UI를 도입했다고…https://t.co/aaQ5vbrm1dhttps://t.co/3viKMFYhxl

— H. Kim (@metavital) October 10, 2021

Google Is Moving Its iOS Apps Toward Platform UI Conventions and Away From Material Design https://t.co/oCoqRhWqj0

— Pixel Envy (@pxlnv) October 9, 2021

I’m pretty interested to see the long term results of this. It seems like Google is saying that matching user’s expectations of the platform is more important than being an identical app across iOS and Android. That’s also React Native’s #1 principle. https://t.co/4T0UGiolX4 https://t.co/CZ380fU4Wi

— Eli White (@Eli_White) October 10, 2021