Windows App Development
Windows software for the desks where the real work still happens.
We build Windows desktop applications in C# and .NET: new products in WinUI 3, and careful modernization of the WPF, WinForms and older systems your staff rely on every day.
What we build for Windows
New desktop applications
Keyboard-driven, multi-window software for people who sit in the same application eight hours a day.
Legacy modernization
WinForms, WPF, VB6 and Access systems moved to supported technology, in stages, while the business keeps running on them.
Line-of-business integration
SQL Server, ERP systems, Active Directory and Entra ID, label printers, scanners and serial devices.
Deployment and fleet management
Signed MSIX packages delivered through Intune, the Microsoft Store or your own update channel.
Where Windows projects are won or lost
Keyboard first
A data-entry clerk notices every extra keystroke, thousands of times a week. Focus order, shortcuts and tab behaviour get specified, not left to defaults.
Migrate in slices
Big-bang rewrites of working software fail often and expensively. We replace one module at a time, with both versions able to run, so there is always a way back.
Deployment is a feature
An application that cannot update itself cleanly across 400 locked-down machines is not finished. Packaging, signing and rollback are designed alongside the first screen.
Tools
The stack we reach for.
- Language
- C#, modern .NET
- Interface
- WinUI 3, Windows App SDK, WPF
- Persistence
- SQLite, SQL Server, Entity Framework Core
- Identity
- Entra ID, Active Directory
- Testing
- xUnit, FlaUI
- Distribution
- MSIX, Intune, Microsoft Store, code signing
Questions we hear first.
Should we rewrite our old application or modernize it?
Usually modernize. Old software contains years of business rules that nobody wrote down, and a rewrite loses them. We audit first, and recommend a rewrite only when the existing code cannot be safely changed.
Can our WinForms or WPF application move to modern .NET?
In most cases, yes. Both run on current .NET, which restores support and improves performance without a redesign. Third-party controls and old dependencies are the usual obstacles, and the audit identifies them up front.
Do we have to use the Microsoft Store?
No. Internal applications are typically deployed through Intune or a signed MSIX on your own infrastructure. The Store is worthwhile for commercial products that benefit from its reach and update handling.
What will it cost?
For modernization, the size and health of the existing code decide it, so we quote after the audit. For new applications, discovery is a fixed fee and ends in a written estimate.