Digital products

Web apps, mobile apps, and tools a team uses every day.

What this work is

I design the screens and write the software for the same product, including empty, error, and loading states. A loose note is enough to start. It does not need a finished specification. What comes back is something a team can open every day, not a throwaway prototype.

The stack follows the job. Recent work has used Next.js, React, Angular, Flutter, FastAPI, etc. Docker, Kubernetes, or Kafka come in when the system needs them. SysHealth Pro is one example: a single health view across mixed infrastructure, including the feeds that stop reporting.

This covers

Web applications
Mobile applications
Internal tools
Dashboards
APIs and integrations
Web applications
Mobile applications
Internal tools
Dashboards
APIs and integrations
Web applications
Mobile applications
Internal tools
Dashboards
APIs and integrations
Web applications
Mobile applications
Internal tools
Dashboards
APIs and integrations
Web applications
Mobile applications
Internal tools
Dashboards
APIs and integrations

Start a project

When it fits

A product a team opens every day, or a tool that replaces a spreadsheet and a chain of messages.

You leave with

Working software, an interface that matches the job, and a structure someone else can change.
A codebase another developer can change
Workflows that match how the team already works
Screens that do not need a guided tour

Projects in this area

2026SysHealth ProInfrastructure

The other three

AI and automationModels and workflows on a real task, including chat over your own knowledge.WebsitesCompany and product sites that load quickly and are easy to extend.Product designInterface design an engineer can build, often because I am that engineer.

Start on Digital products.

Say what you need this to do, who it is for, and what already exists. I reply by email, and we agree scope in writing before work starts.

Start a project