Tip: Enable the Material Design 2 Makeover in Chrome for iOS

Posted on July 28, 2018 by Paul Thurrott in iOS with 3 Comments

With the release of Chrome 68 this week, Google is starting to stealth-deploy a coming user experience refresh that implements the new thinking in Material Design 2.

I already discussed how you can enable this new look and feel in Chrome for desktop, and I couldn’t be happier with the results, especially with the even newer changes I see using Chrome Canary. But now you enable the Material Design 2 refresh on Chrome for iOS too.

To do so, you must be running Google Chrome version 68. So make sure you’re updated in the app store first.

Next, open Chrome and navigate to chrome://flags/#top-chrome-md.

In the screen that appears, scroll down until you find the option “UI Refresh Phase 1.” Then, enable it using the box on the right.

Hard close Chrome and then relaunch it. As you can see, the user interface at the top has been refreshed with the new style, which includes the curved tabs and a new button style.

Android user? Chrome is still stuck on version 67 as I write this, so I assume this change will be coming soon to that platform too, as part of that version upgrade.


Tagged with

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (3)

3 responses to “Tip: Enable the Material Design 2 Makeover in Chrome for iOS”

  1. dontbe evil

    metro ehm… modern ehm… fluent ehm… material design

  2. markbyrn

    You can enable in Android too:



    On Mac, you need to also enable enable chrome://flags/#views-browser-windows in addition to chrome://flags/#top-chrome-md (refresh)

  3. rmac

    With the continued enhancements in Chrome and Edge, effectively pulling the same way and heading in a PWA direction, I wonder where we are we going with OSs and containers? Perhaps the browser will be the 'OS container' of the future, delivering PWAs regardless of the OS? At the risk of going off topic, I also read an interesting article (Rockford Lhotka) on Xamarin being made to run with WebAssembly. That got me thinking, why would we need Xamarin if the browser acted as the app container?

Leave a Reply