Microsoft Rebrands UI Fabric to Fluent UI

Microsoft announced today that it is renaming UI Fabric to Fluent UI to simplify and consolidate its design language branding.

“We’re simplifying our story to collectively rally around a single UI library for our web components, Fluent UI,” the Microsoft 365 Team writes in a new post to the Microsoft 365 Developer Blog. “We’ve evolved Microsoft to speak a common language through a shared design system. Fluent UI will directly connect that effort to a broad set of products, through code, specifically the convergence of our most used web engineering frameworks, Fabric and Stardust.”

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Confused? You’re not alone. So let me try to muddle through this.

Microsoft describes Fluent, broadly, as its “design-to-code system.” It’s a “coherent, efficient, and effective” foundation that’s shared by design and engineering, and to date, it’s been most closely associated with the Fluent Design System, which is the design part of that foundation, a common user experience that (hopefully) works across multiple endpoints and form factors.

Fluent UI hits on the engineering end of the Fluent spectrum, as I understand it. It is replacing two previous frameworks, Fabric and Stardust, the former of which I believe was originally called Office Fabric.

“This [change] allows our teams to collectively work together on a shared code base with a shared set of build and development tools to support our products and community more efficiently,” the post continues. “It also allows us to get to a single UI library for Microsoft 365.”

The first major release of the newly-renamed Fluent UI is expected in summer 2020, Microsoft says. After that, it will focus on performance and theming.

Tagged with

Share post

Please check our Community Guidelines before commenting

Conversation 7 comments

  • christian.hvid

    13 March, 2020 - 3:09 pm

    <p>While it's encouraging that Microsoft is finally working towards a coherent design system, like Google has Material Design and Apple has whatever-their-abomination-is-called, perhaps it would make sense to redesign first and rename later? UI Fabric looks nothing like Fluent UI (Fabric looks a lot better, IMHO), so having them share the same name is bound to be confusing.</p>

  • Rob_Wade

    13 March, 2020 - 5:41 pm

    <p>I find this all humorous. Pointless and humorous. As with all their previous "design languages" and "branding", this will last a day or two and then they'll be off to something else that is as fluffy and inconsequential to the user. They already crapped all over the Windows 8 experience — which I loved immensely, by the way — in favor of going backward, in my opinion. But I have no confidence in whatever their plans are because you can't depend on anything they're doing to have any sort of staying power. They don't care about consumers, in the end.</p>

  • Truffles

    13 March, 2020 - 8:18 pm

    <p>Lets hope fluent isn't effluent and makes us affluent.</p>

    • Paul Thurrott

      Premium Member
      14 March, 2020 - 8:35 am

      love it

  • Usman

    14 March, 2020 - 7:33 am

    <p>UI Fabric / Office Fabric, is the UI used in and many O365 applications. </p><p><br></p><p>Around 2017, they had Office Fabric and Microsoft Web Framework. </p><p><br></p><p>Eventually 2 years later they decided to build on top of Office Fabric, and rename it to UI Fabric.</p><p><br></p><p>Fluent is a design language, it has changed over the years from 2017, first it was transparency and depth, it was also Windows only. The priority focussed away from transparency, more towards depth, curves, flat colours / glowing gradient.</p><p><br></p><p>Fluent then took influence from Office Fabric and most of fluent design was starting to be dictated from the Office Fabric UI Team. It made sense to take an existing and widely used UI framework + components that were being used across Office 365 applications rather than to start one from scratch.</p><p><br></p><p>Office Fabric became Fabric UI because it was used across other Microsoft services like Azure Dashboard, Microsoft Partner Network, Azure DevOps etc.</p><p><br></p><p>The Fabric UI was then updated with fluent design consistency, such as rounded corners, borders around squircles, common radius for curves, shorter pill length etc.</p><p><br></p><p>Now we're here, renamed to Fluent UI , a web framework that looks consistent and is used across many Microsoft Web services.</p>

  • rmac

    14 March, 2020 - 3:45 pm

    <p>Another step in the right direction, but just look at this MS artwork which has become endemic across the entire MS tech sites: pointless, indistinguishable and unmemorable, it conveys precisely nothing. </p>

  • scottkuhl

    14 March, 2020 - 10:32 pm

    <p>The fact that all the useful components of this framework are built on React is very limiting to its adoption. I still don’t understand why the Office team is steering all Microsoft web design down that road. They should have made it more agnostic like Bootstrap. But then search for WinStrap and what a disaster that was. At least there seems to be some movement toward web components but not much.</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2023 Thurrott LLC