Microsoft Fluent Design System
microsoft.com
microsoft.com
On the hardware side, their Surface line is beautiful. But the modern Windows UI/UX is...uninspired and sterile. So is Edge, Explorer, and Office suite.
Google and Apple are the leaders in the application design space re. UI/UX, and I just don’t see Microsoft treating it seriously just yet.
Google and Apple are not much better. Neither have upgraded to Flat 2.0 [1] although Apple is slowly moving in that direction in the post-Jony-Ive era.
Apple's name used to be synonymous with good design. But that was back when Jobs was still around.
[1] "Google’s Material design language is one example of flat 2.0 with the right priorities: it uses consistent metaphors and principles borrowed from physics to help users make sense of interfaces and interpret visual hierarchies in content."
As a designer, I feel truly inspired by Apple’s UI even today. Google tries to get design but their company goals do not place user experience on as high a pedestal as Apple, and they are always a little behind.
My two cents.
Ironically, their hardware is the one of few good things about them, but even that is starting to slip now IMHO.
For example, their last month Surface update. It seemed them going absolutely crazy with "details," but half an hour into the event and you can start see how poorly thought through the design was.
Just like Apple's early product, they are very "substance over essence." They add a lot of fancy features, but they themselves have poor idea what for they are.
https://getbootstrap.com/docs/4.3/components/alerts/
Perhaps a gallery of example websites & apps could help a lot. That was the first thing I was looking for. Couldn't find any, so I had to drill into the docs in hopes of finding some case-by-case examples of each UI element. It really helps me to get going on frontend design, especially on a new framework, when I can see a completed sample that has some similarities to what I want layout-wise in my design.
The most direct Fluent Design System library to consider compared to Bootstrap would be Fabric UI which covers Web, iOS, and Android:
https://developer.microsoft.com/en-us/fabric#/
Up until recently Fabric UI didn't always match Fluent Design goals, but they've aligned to Fluent a lot more over recent releases.
Though, generally the "closest to homebase" implementation of Fluent Design is often regarded to be the WinUI library that is the basis for most "modern" UI controls in Windows, in particular its where you see the most of some of the exotic materials Fluent Design likes such as the "acrylic" backgrounds that a lot of people really associate with Fluent:
No matter what design they pull over their software, it will not make genuinely substandard software cool.
The homepage is useless, but the real docs are decent https://docs.microsoft.com/en-us/windows/uwp/design/
Sadly, Microsoft still does not provide guidance or necessary APIs to desktop app developers (e.g. those primarily using .NET, Win32, WPF, WinForms, etc) to implement Fluent Design elements/controls.
I'm hopeful we'll see a change here, but fear it'll happen too late, that is, before another design language is introduced.
I feel like the guidance is clear enough at this point: migrate to WinUI 3. If you can't migrate your app "all the way" to UWP today, you can use XAML Islands in Win32 apps and embed UWP/WinUI XAML in places that are appropriate. Some common WinUI controls that you might want to use have easy to find wrappers on NuGet to do most of the XAML Island magic for you for WPF and WinForms applications.
WinUI 3 has yet to be released. (It's only barely in alpha now.)
If you are already using XAML, the WPF => UWP XAML transition shouldn't be so much of a hurdle as to be a "non-starter in most cases". In most Enterprise CRUD the biggest problem is DataGrid, but you pull one in from the Community Toolkit or one of the 3rd Party components vendors like Telerik. WinUI is talking about first party formally "Fluent" productizing the Community Toolkit's version sometime later in the 3.x timeline.
Of course, my view of it is biased by doing a bunch of WPF <=> Silverlight XAML transition work by hand for a few years, and compared to that era, WPF <=> UWP is a lot more civilized.
> WinUI 3 has yet to be released. (It's only barely in alpha now.)
I forgot that part. Just replace WinUI 3 with WinUI 2 for "today" (up until 20H1, supposedly), and my statement stands.
Example:
https://static2.sharepointonline.com/files/fabric/fabric-web...