Idea No. 16: Combine Material and Fluent Designs

Google's Material design is beautiful. Microsoft's Fluent design is beautiful. Now what if we can have both of them in one beautiful Material Fluent or Fluent Material design? And what if it gets developed and maintained as the global standard UI/UX guidance.

Every app has its own way of presenting itself. There are many experiences that can be invented out of this freedom. However, for new apps not (yet) focusing at this level of branding, there are ways to offer successful primary UI/UX through tried and proven practices. If these can be compiled to basic guidelines, that's what Material + Fluent design can be all about.

Google and Microsoft has to admit that both of their design guidelines are good. Their pros (and cons) can be merged and sanitized in to a unified guidance for all app developers targeting any platform including desktops, mobile, web, consoles and IoT.

If you're wondering, where's Apple in this picture? Take note that Apple operates in a closed ecosystem. Apple's design guidelines revolve around their own hardware and software design goals. It is safe to say that Apple's UI/UX guidelines are intended to please Apple's own branding.

Google and Microsoft are already playing the cross-platform game in their products and services. This fact makes Material and Fluent the likely candidates to combine successfully.

Google's Material design successfully champions data to be the central driver and motivation of the presentation. Microsoft's Fluent design champions strategic use of ambient, subtle or bold visual and audio capabilities to the experience. Both Material and Fluent are effective in 2D (display screens) and 3D (AR/VR) devices. Combining these strengths in to one design guideline would be beneficial to all cross-platform developers.

We need a universal UI/UX design language that can serve as a basic but also standardized guidance for all developers. It doesn't mean to limit. It doesn't mean to enforce. More important, it doesn't mean to brand. It is meant to provide a good place to start with, out of which we can expect unique UI/UX to be built. But on its own, with just the basics, we can already expect it to be good for everyone.

Comments