What is Flow.Launcher built with?

Flow.Launcher is a C# repo built with F#, CommunityToolkit.Mvvm, and Microsoft.Extensions.Hosting. It stores its data in SQLite, makes its content with Svg.Skia, is tested with Microsoft.NET.Test.Sdk, NUnit3TestAdapter, nunit, and Moq, deploys with NLog, and uses Microsoft.Data.Sqlite, BitFaster.Caching, and Microsoft.Extensions.Caching.Memory. It has 60,212 written lines, with 26 test files.

Read on November 7, 2026, at commit ff99ea0. Read it as markdown

Frontend

Interface 4

  • Microsoft.Toolkit.Uwp.Notifications1 file
  • SkiaSharp1 file
  • AvalonEdit
  • VirtualizingWrapPanel

Backend

Data 4

Support

The base 3

Content 1

  • Svg.Skia1 file

Testing 4

  • Moq2 files
  • nunit26 files
  • Microsoft.NET.Test.Sdk
  • NUnit3TestAdapter

Deploy 1

  • NLog3 files

Tools 2

  • Fody
  • Microsoft.Windows.CsWin32

Other 6

  • Microsoft.VisualStudio.Threading7 files
  • Microsoft.Extensions.DependencyInjection1 file
  • Microsoft.IO.RecyclableMemoryStream1 file
  • SharpZipLib
  • System.Drawing.Common
  • TaskScheduler

Other repos with a similar stack

Ordered by how much of its stack they share with Flow.Launcher, then by stars.

Frequently asked questions

What language is Flow.Launcher written in?
Flow.Launcher is written in C#, with 60,212 written lines.
What framework does Flow.Launcher use?
Flow.Launcher is built with F#, CommunityToolkit.Mvvm, and Microsoft.Extensions.Hosting.
What database does Flow.Launcher use?
What services does Flow.Launcher use?
Flow.Launcher uses Microsoft.Data.Sqlite, BitFaster.Caching, and Microsoft.Extensions.Caching.Memory.
Does Flow.Launcher have tests?
Yes. Flow.Launcher has 26 test files and is tested with Microsoft.NET.Test.Sdk, NUnit3TestAdapter, nunit, and Moq.
Which repos have a stack like Flow.Launcher's?
The ones that share most of its stack:jellyfin/jellyfinShareX/ShareXBeyondDimension/SteamTools

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →