Windows Fluent Design Concept
Last Updated on August 23, 2026 by Editorial Team
A beautiful concept that includes 28 screens:
- Start 01
- Start 02
- Search 01
- Search 02
- Action Center Today
- Action Center Notification
- Alarm Clock 01
- Alarm Clock 01.1
- Alarm Clock 02
- Alarm Clock 03
- Alarm Clock 04
- Groove 01
- Groove 02.1
- Groove 02.2
- Groove 02.3
- Calling 01
- Calling 02
- Movie Player
- News 01
- News 02
- Photos 01
- Photos 02
- Photos 03
- Sticky Notes 01
- Sticky Notes 02
- Sticky Notes 03
- Store 01
- Store 02
Created by jeans studio
What you’re looking at here is a genuine cross section of the Windows 10 experience rebuilt through the lens of Fluent Design, the visual language Microsoft introduced to bring depth, translucency, and motion into what had been a fairly flat, tile-driven interface.
You can see that shift immediately in the layered windows across the preview: the Alarms & Clock panel sits on top of the Photos app, which sits on top of the Groove music player, each one slightly offset with soft shadows separating them.
That stacking is the whole point of Fluent Design. It uses acrylic blur, translucency, and light to give the operating system a sense of physical depth rather than a stack of flat rectangles.
The color story stays close to what shipped in real Windows builds at the time: mostly white and light gray chrome for productivity apps like Store and Photos, punctuated by rich, saturated imagery in Groove, News, and the movie player where album art and film stills carry the color.
Typography leans on Segoe-style system type, clean and utilitarian, which keeps the focus on content rather than decoration. That restraint is very much in character for Windows: the UI gets out of the way and lets photos, album covers, and news thumbnails do the visual work.
For anyone studying or presenting native Windows patterns, this concept works as a reference library more than a single mockup. The 28 screens cover the everyday building blocks of a desktop OS: a Start menu, search, notifications, alarms, a media player, a calling interface, a news reader, a photo gallery, sticky notes, and an app store.
That range makes it genuinely useful for a few different kinds of work.
- UX portfolios that need to demonstrate familiarity with platform-specific design systems and native app conventions.
- Windows app or UWP concept projects where you need believable system chrome around your own app screens.
- Presentations and case studies where you want to show a redesign next to the “before” state of a real OS feature.
- Design system documentation for teams building Fluent-style products, where having reference screens speeds up onboarding new designers to the visual rules.
Working With the Fluent Style
If you plan to adapt these screens rather than use them as reference, keep the acrylic and depth cues intact, since they’re what signal Fluent Design at a glance.
Swap in your own content first: album art in Groove, photo grids in the Photos app, headlines in News. Keeping the existing layout and spacing while replacing imagery is the fastest way to see how your content behaves inside this system.
When you do want to restyle a screen, adjust blur and opacity on the background layers before touching color, since translucency is doing most of the work in making these windows feel layered rather than flat.
Try to preserve the contrast between light UI chrome and dark, image-heavy content panels. That contrast is what makes the Store, News, and Movie Player screens feel alive against the more neutral Alarm Clock and Sticky Notes windows.
If you’re building out a larger case study, pairing these screens with your own custom icons, a Segoe-adjacent typeface, and a consistent accent color will help unify the set into something that reads as a coherent product rather than a collection of disconnected windows.