Build & improve your app - An engineer for the software you're building

Whether you are starting something new or building on an app you already have, you need an engineer to move it forward. Perhaps a previous developer left it behind, or it works but is getting harder to change, or you simply need something built. That is the work I take on.

01

An app you built with AI that has outgrown the tool

AI coding tools are genuinely good at building the first version of an app. They get less reliable as it grows, for one reason. The app becomes bigger than the tool can hold in view at once, so it starts breaking things it cannot see. You will recognize it when it happens. A change that works on your computer but will not go live. A fix that breaks something else without saying so. Evenings spent repairing instead of building. That is not you doing it wrong, and it is not a reason to start over. It means the app has reached the point where it needs an engineer. I take over the code you already have, make it safe to change again, and build from there. You keep deciding what the app should do. I handle how it gets done.

Why this happens, and what you can do about it →
02

New features on an app you already have

You have a working application and a list of things it still needs to do. I pick up your existing code, learn how it fits together, and build new features the way the rest of the app is built, so what I add reads like part of the app rather than something attached to it. You get features shipped on a schedule that fits your business, without breaking what already works.

03

Modernizing and upgrading older code

Software ages. The tools underneath it stop being supported, the parts it depends on stop getting security fixes, and code that made sense two years ago starts slowing everything down. I upgrade older code carefully and in stages, so you end up on current, supported foundations without one risky rewrite and without breaking what already works for your customers.

04

Mobile apps for iPhone and Android

I build mobile apps once rather than twice: one project that runs on both iPhone and Android, instead of two separate builds to pay for and keep in step. New apps, or fixes and new features on a mobile app you already have. I built and published UnityPay, a personal-finance app that connects to real bank accounts, and Albie, a golf swing analysis app, so this is work I have shipped, not a line on a résumé.

See UnityPay →

Where this helps

If any of these sound like where you are, this is the kind of work I do:

  • An app you built with AI that has started fighting you. Changes that work on your screen but won’t go live, or fixes that quietly break something else. The app has outgrown the tool that built it.
  • Something new built from scratch. A site or an app you need built, designed and delivered by one engineer, start to finish.
  • A feature you need built. Something your app still needs to do, built into the app you already have.
  • An outdated framework or dependencies. Older code brought up to current, supported versions, safely and in steps.
  • Code a previous developer left behind. An app you inherited, taken on and moved forward.
  • Code that's hard to change. Tangled or fragile code reorganized, without changing what it does, so it is safe to build on again.
  • Someone who stays with it. An app that needs someone reliable for ongoing changes and fixes as your business grows.

Built on .NET, comfortable across the rest

My core stack is C# and .NET, the same foundation a lot of business software is already built on, with .NET MAUI for cross-platform mobile. But I work comfortably across the stack: TypeScript and React on the front end, Node.js and Express for APIs, SQL Server and Postgres for data. And when the work is getting your app deployed, secured, and kept running, the language it’s written in matters far less. I take on apps built in just about any stack and get them live on infrastructure you own.

Every project is different, so I quote this work per project. Tell me what you have and what you need, and I’ll come back with a plan and a price.

Twenty minutes, and no pitch.

I'll tell you what I'd fix first in what you've built, and why. No pitch.