New Windows Look and Feel, Neon, Is Officially the 'Microsoft Fluent Design System' (arstechnica.com)

An anonymous reader quotes a report from Ars Technica: Earlier this year, pictures of a new Windows look and feel leaked. Codenamed Project Neon, the new look builds on Microsoft Design Language 2 (MDL2), the styling currently used in Windows 10, to add elements of translucency and animation. Neon has now been officially announced, and it has an official new name: the Microsoft Fluent Design System. The switch from "design language" to "design system" is deliberate; Fluent is intended to define more than just the appearance, but also the interactivity. Though visually there are common elements, the system is designed to work across virtual/augmented reality, phones, tablets, desktop PCs, games consoles, using mice, keyboards, motion controllers, voice, gestures, touch, and pen, with the interactivity and input optimized to each particular form factor. Fluent is described as having five "fundamentals": light, depth, motion, material, and scale. "Light" means that the interface should avoid distracting and strive to ensure that attention is drawn to where it needs to be. With "depth," Fluent apps will make greater use of layering and the relationships between objects and interface elements. Fluent will use "motion" to indicate relationships and connections between elements, establishing context. Microsoft is using "Material" to mean making best use of the screen space and giving room to content. "Scale" means building interfaces that can go beyond two dimensions, and go beyond the size of a screen, to embrace new form factors and input methods as they arrive.

Comments

No no no NO NO NO NO

[the_skywise]

Though visually there are common elements, the system is designed to work across virtual/augmented reality, phones, tablets, desktop PCs, games consoles, using mice, keyboards, motion controllers, voice, gestures, touch, and pen, with the interactivity and input optimized to each particular form factor.

1000 times NO - you cannot use the same definition language across different input strata. You either end up with a least common denominator of interactivity or you sacrifice one for the utopian goals of the idealogy (That is to say Windows 8 and Metro). Its always a grand idea in theory because you immediately think "It's just buttons and scrolling.. how hard can that be?!". It's not - it's text and selection and finding the items you want vs need vs trying to recall the interface paths to access them plus the needs of the input device you're working with. A VR system isn't going to acommodate the subtleties of a touch screen (though they'll try) and a touch screen drops the finer gesture control of a pen which is simillar (but not the same as) a mouse interface. You need a CUSTOM UI and access strategy per device type that interfaces to the underlying control scheme. That's why the iOS is DIFFERENT than MAC OS and not a one-size fits all strategy like Windows 10 which does NOTHING well (and don't even get me started on that craptacular Xbox One UI)

Re:No no no NO NO NO NO

[mikael]

A mouse has two or more buttons that send press and release events, and also sends out motion events. A trackball will do the same, so you can do things like hover over buttons and not press them. A touchscreen will have multiple fingerpress and fingerrelease events. Then these can be combined into gestures like double slide, single slide, two finger zoom, two finger pinch, two finger rotate, two finger translate. These could go up to any number of events, such as the screen swipe with the palm of your hand to capture a screenshot. But there is no concept of hover. Something is either pressed or there is no event. You can add delays and timeouts but that's about all. With VR and AR, you can do gestures like head tilt to move or turn in different directions, various button presses using the headset buttons or stare and select. If you have a VR glove or set of globes, then there are all the hand gestures that could be made. It's easy to map these onto classic mouse events, but hard to have a single event handler for everything.

Whatever

[Opportunist]

Can we get an update where we get to decide when to reboot our machines and what info to send to Redmond? Just 'cause you paint the turd in flashy colors doesn't make it smell better.

Paint the turd.

[Anonymous Coward]

Shiney new shit all over the shop, but File Explorer STILL cannot handle the files with long paths *that it itself creates*.

It has had this problem for over a DECADE FFS !

Fix the broken windows. Then polish them !

Captcha: "systemic" as in "bugs"

Deep inside Redmond

[Imazalil]

mid-level manager 1: I love what google is doing with this material design, they cribbed some of our metro stuff but took it to a whole new level.

mid-level manager 2: true dat, but I prefer the soft and smooth translucency Apple has in iOS and macOS.

mid-level manager 1: hmmm...

mid-level manager 2: hmmmm...

mid-level manager 3: why not both?!

mid-level manager 1: but won't we be accused of just copying their stuff?

mid-level manager 2: just throw in some bull about holo-lens and synergy, and everyone will be distracted thinking about drawing dongs in 3d.

mid-level manager 1: genius!

What for?

[jbmartin6]

"elements of translucency and animation"....I hate it already. For a while there, it looked like MS was starting to understand that people use applications, not the OS. The only goal of the OS is to make it easy to use applications and stay out of the way otherwise. They sort of got the hint with the Vista fiasco. Looks like everyone who got it has retired and the latest shiny thing crowd is back in the saddle.