Much news was expected about Microsoft Fluent Design System by Microsoft after the numerous design leaks and sneak peak by MS itself through its apps in Windows 10.
Microsoft’s Build 2017 was held in the 2nd week of this month and it is the Annual Developer Conference of Microsoft that is attended by developers from throughout the world and much more join in through the live stream as well.
Though the event mostly focuses on the relation of Microsoft with its Developers, a few consumer eccentric features also come in the highlight.
Windows 10 as is Microsoft’s Goal of running One OS across a range of devices and form factors to ultimately provide a Coherent Experience to its user.
The current iteration of Windows 10, right from its initial preview to Windows Insiders has mostly been a Structural Backend Change to its Core ( or OneCore that’s what Microsoft calls it at least ).
Although there has been a New Design Changes and Pattern mostly resembling Android and iOS designs, so as to get their developer attention into developing them for Windows.
In spite of this, the core OS and Application design were in need of an overhaul that would scale accordingly with the device and its OS. The design would have to be something that would encourage both the user and developer alike to get into the experience of using or developing it just like Google achieved with its Material Design overhaul of Android OS and Apple with its iOS 7 overhauls in visual design.
The answer to all this came in the form of Fluent Design System ( internally codenamed “Project Neon” ) by Microsoft in Build 2017.
What exactly is Microsoft’s Fluent Design System?
At its heart, Fluent Design System is composed of 5 basic design elements and pattern that help the user to feel a level of depth and achieve a level of perception while engaging him/her in the OS/App experience.
Those building blocks as stated by Microsoft are as follows:
All in all, Microsoft’s Fluent Design System is one that will enable to provide the end user with a cohesive app experience into the Microsoft Ecosystem.