I work with a small number of clients at a time, which means you deal
with the person writing the code. Most projects start with one of these
three, and plenty of them end up being all three.
App development
Apps that meet people where they already are — in a browser, on a phone, on a kiosk screen.
Not every app belongs in an app store. I build web apps, installable progressive web apps, and native mobile apps, and I'll tell you honestly which one your idea actually needs. The goal is software that loads fast, works offline where it should, and doesn't ask anyone to create an account before it's useful.
Web apps and progressive web apps
Native and cross-platform mobile
APIs, integrations, and the backend behind them
Design and build from a blank page, or rescue something half-finished
Consulting & technical advisory
A second opinion from someone who will actually be building things like it.
Before you commit a budget to a platform, a vendor, or a rewrite, it helps to have someone independent look at it. I review architectures, scope projects into something buildable, evaluate the tools you're being sold, and translate between the technical team and everyone else.
Architecture and technology selection
Scoping and estimating before you commit
Vendor and platform evaluation
Code and security review of existing work
Ongoing support & maintenance
Shipping is the start. Someone has to keep it running.
Software rots quietly — dependencies age, certificates expire, platforms change their rules. I keep the things I build (and things I didn't) patched, monitored, and moving forward, so a small problem stays small.