# FluentFlyout Review: A Fluent 2 Flyout App for Windows 11 Media and Lock Keys

> FluentFlyout replaces Windows 11's media popup with a Fluent 2 flyout, a taskbar widget and a lock key indicator. It ships through the Microsoft Store or a signed .msixbundle, and the source is GPL-3.0.

**unchihugo/FluentFlyout** — The modern Flyout app for Windows 11, built with Fluent 2 Design principles. Media Flyouts, Taskbar Widgets and more.

- Repository: https://github.com/unchihugo/FluentFlyout
- Website: https://fluentflyout.com
- Stars: 4,612 · Forks: 223
- Language: C#
- License: GPL-3.0
- Published: 2026-09-23 · Updated: 2026-09-23 · Language: en
- Canonical page: https://hysenlabs.com/projects/unchihugo-fluentflyout

## The Windows 11 media popup problem FluentFlyout targets

Windows 11 draws a small media control panel in the corner when you press a media key. It disappears on its own, it carries no Up Next information, and it does not tell you whether Caps Lock or Num Lock is on. FluentFlyout exists to replace that surface with popup flyouts built from Fluent 2 components, plus a taskbar widget that keeps media information visible without waiting for a keypress. The README describes the goal as blending into Windows 11 so the controls feel native rather than bolted on.

The audience is narrow and specific. You need Windows 11, you care about how the system chrome looks, and you want media state and lock key state reachable from the system tray. Users on Windows 10 are outside that group: the README never lists Windows 10 as supported, and the design language it imitates is the Windows 11 one. The repository carries translated READMEs in Simplified Chinese, Dutch, Turkish, Russian and Korean, and the badge row links a Weblate project, which tells you the maintainers expect a non-English user base.

## How the flyouts, taskbar widget and Up Next panel fit together

The repository splits into FluentFlyoutWPF, which holds the application, FluentFlyout.SourceGenerators, which holds build-time code generation, and FluentFlyoutMSIX, which packages the app for MSIX distribution. That layout is the clearest signal of the architecture: a WPF desktop application that is packaged rather than a service or a shell extension. A .sln file sits at the top level, so the whole thing builds as one Visual Studio solution.

The feature list maps onto distinct UI surfaces. The audio flyout shows cover art, title, artist and transport controls. The Up Next flyout appears when a track is about to end and shows what follows. The lock keys flyout reports the state of the lock keys. The taskbar widget puts media information directly on the Windows taskbar. Repeat All, Repeat One and Shuffle are exposed as controls, and the app supports customizable flyout positions, light and dark mode, and matching the device color theme. The README also states the app uses Windows Mica blur and sits in the system tray.

What the README does not describe is how the app reads media session data. There is no mention of a specific Windows API, no plugin model, and no statement about which players are supported. If you need to know whether a particular music client will feed the flyout, the README is silent and you would have to check the source or try it. That is a real gap for anyone evaluating it against a player that does not publish media session information to Windows.

## Installing FluentFlyout from the Microsoft Store or a signed bundle

The README calls the Microsoft Store route the recommended one and links the store listing directly. If you use it, there is no command to run and no certificate to handle: the store manages installation and updates.

The manual route starts at the project's download page, where the README says to download the manual installer labeled GitHub release (x64) and then run the batch file. The README gives the filename explicitly:

```bash
FluentFlyout_Installer.bat
```

Running that file and following its prompts is the whole procedure. The README also offers a path that skips the installer entirely. For that you download the .cer certificate, open it, choose Install Certificate, select Local Machine, grant admin access, place the certificate in Trusted Root Certification Authorities, and finish the wizard. Then you download the .msixbundle and let App Installer handle it, pressing Install or Update depending on whether FluentFlyout is already present. The certificate step is not optional in that path, because the bundle is signed and Windows will not install it otherwise.

## A first run: what you configure after the flyout appears

Once installed, FluentFlyout starts in the system tray. The README's feature list is the best guide to first-run configuration, because it names the settings that exist: flyout position, light or dark mode, and matching the device color theme. Those are the knobs a new user touches first, and they are described as personalization settings rather than defaults you must accept.

There is no command-line interface documented, and no configuration file format appears in the README or the repository listing. Settings live inside the application. So a first real use looks like this: start playback in a media application, press a media key or open the flyout from the tray, and confirm that cover art, title and artist appear. Then check the lock keys flyout by toggling Caps Lock. If the taskbar widget is enabled, it should show media information without any keypress.

If nothing appears, the README offers no troubleshooting section. The repository does not document a log location or a diagnostic mode. That is worth knowing before you spend time on a silent failure.

## Where FluentFlyout stops being the right tool

The installer path is the sharpest limitation. Trusting a root certificate on your machine is a meaningful action, and the README walks through it without discussing what the certificate identifies or when it expires. Anyone installing on a managed corporate device should expect that step to be blocked by policy, and the Microsoft Store route may be blocked too. Neither path is designed for silent deployment.

The second limitation is platform scope. The project is a Windows 11 app. Nothing in the README claims Windows 10 support, and the Fluent 2 and Mica elements it relies on are Windows 11 features. If your fleet mixes Windows 10 and Windows 11 machines, this does not cover the older ones.

The third is the missing integration detail. Because the README does not say which media APIs or players are supported, you cannot predict coverage from the documentation alone. A player that does not surface a media session to Windows may simply never trigger the flyout, and the README would not have warned you.

Finally, the licence is GPL-3.0. That is fine for personal use and for anyone distributing under the same terms, but it constrains reuse inside a closed-source product. The repository also carries a PRIVACY-POLICY.md, which is worth reading before you decide what data leaves the machine.

## FluentFlyout compared with ModernFlyouts and other flyout replacements

The closest point of comparison is ModernFlyouts, the older open source project that replaced the Windows volume and media flyouts. The difference is one of scope and target. ModernFlyouts was built around the pre-Windows-11 flyout surfaces and aimed to modernize them. FluentFlyout starts from Fluent 2 and Windows 11 as given, and adds surfaces ModernFlyouts did not have: a taskbar widget that shows media information persistently, and an Up Next flyout that previews the following track.

The other difference is distribution. FluentFlyout ships through the Microsoft Store and through a signed .msixbundle with a documented certificate step. That is a heavier install than dropping a binary, and it is also the reason updates are managed rather than manual. The README does not document rollback, so if you install a release that misbehaves, the documented path back is not described.

If your requirement is a flyout replacement on Windows 10, or a tool you can compile from source with no signing infrastructure, FluentFlyout is the wrong shape. If your requirement is media and lock key state presented in Windows 11's own visual language, including on the taskbar, it addresses a surface the alternatives largely ignore.

## Maintenance cadence, releases and the GPL-3.0 obligation

The last push to the default branch was on 2026-09-22, one day before this writing, and the most recent release is v2.15.0 from 2026-09-07, titled Enhanced Taskbar Widgets & More. Two earlier releases in the same series, v2.14.0 and v2.13.1, landed in August and July 2026. That is a roughly monthly release rhythm across the visible window, and the repository is not archived.

Upgrade cost depends on the install route. The Microsoft Store handles updates itself. The manual and .msixbundle routes put the update decision on you: the README's step seven says App Installer will offer Install, or Update if FluentFlyout is already installed. There is no documented downgrade path, and no release channel beyond the tagged releases. If you pin a version for compatibility reasons, the documentation does not tell you how to hold it.

The licence is GPL-3.0, stated in the LICENSE file. Redistributing a modified FluentFlyout carries source disclosure obligations under those terms. Running it on your own machine does not. This is a description of the licence, not legal advice; check the full text if you plan to ship anything derived from it. The project also maintains a PRIVACY-POLICY.md at the repository root and accepts translations through Weblate, which shapes what contributions the maintainers expect.

## Conclusion

Adopt FluentFlyout if you run Windows 11 and want media controls, an Up Next panel and lock key status in flyouts that follow the system theme. Skip it on Windows 10, which the README never claims to support, and skip it if you need a build you can audit and compile yourself without setting up the .NET toolchain the repository assumes. Before installing, verify the .cer file's publisher against the certificate instructions in the README, since the manual route asks you to trust a root certificate on your machine.

## FAQ

### Is FluentFlyout free?

Yes. The README presents the Microsoft Store listing and the manual installer as the two ways to get it, with no paid tier mentioned. The source is published under GPL-3.0.

### How do I install FluentFlyout?

The README recommends the Microsoft Store. Otherwise you download the manual installer from the project's download page and run FluentFlyout_Installer.bat, or install the .msixbundle after placing the .cer file in Trusted Root Certification Authorities.

### What is FluentFlyout?

It is a Windows 11 flyout application built with Fluent 2 design principles. It provides an audio flyout with cover, title, artist and media controls, an Up Next flyout, a lock keys flyout, and a taskbar widget that shows media information.

### Is FluentFlyout legit?

The project publishes its source under GPL-3.0, ships through the Microsoft Store, and signs its .msixbundle. The manual install path requires you to trust its certificate, and the README does not describe what that certificate identifies.

### How is FluentFlyout different from ModernFlyouts?

FluentFlyout targets Windows 11 and Fluent 2 specifically, and adds a taskbar widget and an Up Next flyout. ModernFlyouts addressed the earlier Windows flyout surfaces. The README itself does not compare the two.

## Sources

- [License: GPL-3.0](https://github.com/unchihugo/FluentFlyout/blob/master/LICENSE)
- [Project website](https://fluentflyout.com)
- [README](https://github.com/unchihugo/FluentFlyout/blob/master/README.md)
- [Releases](https://github.com/unchihugo/FluentFlyout/releases)
- [unchihugo/FluentFlyout on GitHub](https://github.com/unchihugo/FluentFlyout)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/unchihugo-fluentflyout