Web application development
Dashboards, client portals and internal tools that replace the spreadsheet everyone is quietly afraid to touch.
A web app is where the interesting failures live: permissions, data that has to stay correct under concurrent edits, integrations that go down at the worst moment. I build these with a .NET backend and a React or Next.js frontend, with the boring parts — auth, validation, logging, tests — treated as part of the job rather than a later phase.
What's included
Real authentication and roles
Proper login, sessions and permissions, so an ordinary user can't reach admin data by editing a URL.
A backend that holds up
C# / .NET with Clean Architecture and CQRS, PostgreSQL underneath. Business rules live in one place instead of being scattered across the UI.
An interface people can use
React / Next.js, responsive, keyboard-accessible, with states for loading, empty and error — the three screens most projects forget.
Integrations with what you already run
Payments, CRM, email, third-party APIs — connected with retries and error handling, not a fetch call and optimism.
Observability
Structured logs and metrics, so when something breaks at 2am the answer is in a dashboard rather than a guess.
Tests where they matter
Integration tests over real logic and real data paths, so a change next quarter doesn't quietly break billing.
How we'd work
- 01
Scope, in writing
We agree exactly what gets built and what it costs before any code — no creeping invoice, no surprises.
- 02
Ship in slices
Working software every week, not a big-bang reveal at the end. You see progress and can change course early.
- 03
Pay after launch
You pay once the project is live and you're happy with it. No upfront deposit.
Related work
Questions clients ask
How is this different from a website?
A website presents information; a web app does work — users log in, data changes, rules apply. That difference shows up in auth, data integrity and testing, which is most of the effort.
Can you work with our existing system?
Usually yes. I can build a new app against your current database or API, or add a service alongside what you run. First step is reading what's there before proposing anything.
Who owns the code and can our team take it over?
You own it. It's documented, conventionally structured .NET and TypeScript — a developer joining later reads it without a tour from me. Hand-off is part of the work, not a favour.
What if requirements change halfway?
They usually do. Because I ship in weekly slices, changing direction early is cheap. We re-agree scope in writing when a change is big enough to matter.
Do you handle hosting and deployment?
Yes — Docker-based deployment, environment configuration and a deploy pipeline, set up in your accounts so you keep control of it.
Have a project in mind?
Tell me what you're building and where it's stuck. I usually reply within a few hours.