DESKTOP SOFTWARE · READING, BERKSHIRE

We rebuild desktop software until it behaves.

Ashgrove Imports Limited is a desktop application development practice at 8 Mill Lane, Calcot, Reading. We build, repair and maintain business software that runs on a workstation rather than in a browser tab.

Describe your desktop project See our services

An angled desktop application window resting on a steel workbench in a dusk-lit studio.

WHAT A DESKTOP APP BUYS YOU

The framework is an outcome of your constraints.

A desktop app is worth the extra engineering when it needs something a web page cannot reach: a local device, an offline spell, a fixed-seat workflow on a locked-down machine. Ten people using a warehouse scanner station is a different problem from ten thousand people using a public website.

The trade-off is real — installers, updates on machines you may not control, and versions of Windows or macOS you cannot simply ignore. We spend the first conversations on those constraints rather than the interface.

WinUI 3

WPF

Electron

Recommended default for a fresh Windows build. Microsoft's Windows App SDK pairs with WinUI 3 for new native work.

Still a live Windows technology. Long-lived business code that the business depends on is often worth extending in place.

A reasonable landing spot when the team already writes JavaScript and the product must ship on Windows, macOS and Linux without deep OS integration.

Deployment carried by MSIX alongside the Windows App SDK; the modern install and update story.

Mature deployment routes — ClickOnce still fits internal tools that need per-user installation and quiet automatic updates.

Packages are large and the runtime is heavier on the workstation; better for reach than for close hardware work.

Strongest reach for local device access, background services and OS-level behaviour such as file watching.

Full Windows desktop surface, though the platform is Windows-first and macOS parity means a parallel project.

Weak fit when the app has to reach local hardware or behave exactly like a native Windows application.

Criterion rows: deployment · native integration · cross-platform reach Read the technology stack guide

LEGACY MODERNISATION

Old software is modernised while it keeps earning.

Old desktop software is rarely replaced in one clean cut. It gets modernised while it keeps earning: a reporting module replaced first, an authentication layer rewritten second, the UI last or never. The questions to answer are blunt ones.

Which parts does the business actually depend on? Which exist because of a decision nobody remembers? What breaks if we stop supporting an old Windows version?

See how modernisation works

WPF

Windows Presentation Foundation

live

extend in place, do not rewrite

WinForms

Windows Forms line-of-business UI

maintain

stable, low-change tools

ATL

Active Template Library components

maintain

isolate, wrap, then leave

MSIX

Modern Windows package & update story

live

the default for new installs

ClickOnce

Per-user install and auto-update

live

internal tools with minimal ceremony

WPF on Win11

Older WPF estates on current Windows

modernise

stage the work, keep the workflow

Small, staged work survives contact with a live business far better than a big-bang rewrite — particularly where existing workflows are load-bearing.

THE STUDIO AT DUSK

Where the work actually happens.

A dusk-lit studio with three workstations, monitor bezels and brushed racking.

Ashgrove Imports Limited works from 8 Mill Lane, Calcot, Reading, and with organisations across the UK. Proximity still helps for the awkward sessions — sitting with the people who use the tool and finding which part of the workflow nobody documented.

RELEASE ENGINEERING

Shipping a desktop app is its own discipline.

The choice matters more than it sounds. If your staff machines are locked down by IT policy, a deployment route that needs administrator rights will strand the project. We ask about that in the first meeting, before a single screen has been designed.

See how modernisation works

Build

Automated builds linked to source control, so no one signs an installer by hand.

Package

MSIX for a modern install and update story; ClickOnce where per-user installs are the fit.

Sign

Signed packages and approval gates that leave an auditable trail of what shipped when.

Ship

Delivery to the machines that run the order desk — and the discipline to recover cleanly when a driver changes.

Azure DevOps shows up in Windows application delivery because it ties builds, approvals and deployment targets into one auditable flow. Packaging decisions constrain the software design, so the pipeline is drawn before the interface is.

WHO WE WORK WITH

A small practice, working directly with the people who own the software.

Our clients are usually organisations with a working system and a problem attached to it: an internal tool that has outgrown its original author, a Windows product that needs a macOS sibling, a staged move away from an old framework without a stop in production. There is no account layer between the person describing the problem and the person who has to solve it.

If the honest answer is that you do not need a desktop application, we will say so. A browser tool with a local helper service sometimes solves the same problem for a fraction of the cost.

Find our contact details

Describe your desktop project

Three fields. Enquiries arrive by email and get a considered reply, usually with the two or three questions that actually change the shape of a project.