Web, Mobile and Desktop App Development

Applications that do real work - built to be used daily, not demoed once.

I build web applications, mobile applications and desktop software for Windows, macOS and Linux. The common thread is that these are tools people use as part of their job, which puts a premium on the things that are easy to skip: speed, clarity, error handling and not losing anyone's data.

Most of my application work is for businesses replacing a spreadsheet, a legacy tool or a manual process that has outgrown itself.

Start a conversation

Web, mobile and desktop application development illustration

What I build

Across platforms, with the same emphasis on the end user's experience of actually operating the thing.

Web applications and customer portals
Internal business and back-office tools
Mobile applications for iOS and Android
Desktop applications for Windows, macOS and Linux
Dashboards and reporting interfaces

Booking, quoting and workflow systems
Role-based access and permissions
Integrations with systems you already run
Offline-capable and sync-based tooling
Automated testing and deployment

How an application project runs

Delivered in working increments, so value arrives before the end date rather than on it.

1Problem definition

What is the process today, who performs it, and where does it hurt? A surprising number of application requests are solved better by removing a step than by building software for it. I will say so if that is the case.

2Architecture and data model

The data model is the decision you live with longest. I design it up front, with the growth path in mind, before writing feature code.

3Incremental build

The most valuable slice is built and put in front of real users first. You get something usable early and the feedback shapes what follows.

4Hardening

Error handling, validation, permissions, audit trails, backups and load testing. This is the part that separates an application from a prototype.

5Deployment and handover

Deployment pipeline, monitoring, documentation and a support arrangement if you want one.

Getting the user experience right

Business applications are used for hours a day by people who did not choose them. That changes the design priorities completely: keyboard flow, sensible defaults, forgiving validation and fast page transitions matter far more than visual novelty.

I apply UI/UX fundamentals rather than treating design as decoration. Consistent layout, obvious affordances, meaningful error messages and never losing someone's half-finished work. These are cheap to build in from the start and expensive to retrofit.

On the engineering side, the same discipline applies. Applications get built with an eye on the transaction volume they will eventually see, because rewriting a data model under load is one of the more painful things a business can go through. If you are already in that position, legacy code modernisation is the relevant page.

Related services

Web Development

Marketing sites, web applications and everything in between - designed, built, hosted and handed over working.

API Development

REST and GraphQL APIs, integrations and microservices that are documented, versioned and pleasant to consume.

AI Integration

Practical AI added to software you already run - document handling, search, classification and assisted workflows.

Frequently asked questions

Can you build both the web and mobile version?

Yes. Depending on your requirements that may mean a shared codebase or genuinely native applications - I will explain the trade-off in cost and capability rather than defaulting to whichever is easier for me.

Can you take over an application someone else started?

Frequently, yes. I will review the existing code first and give you a straight assessment of whether continuing is cheaper than restarting. Sometimes it is not, and you deserve to know that before spending more.

Do you provide support after launch?

Yes, on a retainer or ad-hoc basis. Everything is handed over documented, so you are also free to take it in-house or to another developer.

What about desktop applications - is that still a thing?

For certain jobs, absolutely - hardware access, offline working, heavy local processing, or environments with restricted network access. I build for Windows, macOS and Linux where the requirement genuinely calls for it.