Web & Interface Design

Every tool I build gets an interface people want to use. I design and build responsive web applications, working equally on desktop and mobile, with a focus on clean layout, usability and user experience. Automation only pays off if the people it is built for enjoy using it.

Give every automation or AI tool a clean, responsive interface rather than a raw script or an API.

Design for real use: clear layout, sensible flows, and an experience that does not need a training session.

Build the design and the front end together, so what is designed is what actually ships.

Design and build as one

I design the interface and implement it myself, which keeps layout, motion and responsiveness realistic instead of a mockup someone else has to reinterpret.

Desktop and mobile from the start

Responsive behaviour is part of the design, not something retrofitted once the desktop version is finished.

Take the experience seriously

A tool that automates a process still has to be pleasant to use. Getting that right is what makes people adopt it instead of avoiding it.

Do you design as well as develop?

Both, and I prefer to do them together. Designing and building the same interface means the visual design, the motion and the responsive behaviour are tested for real rather than handed over as a static file.

Why does interface design matter for an automation project?

Because adoption decides whether the automation delivers anything. If the tool that digitalises a process is unpleasant to use, people work around it. A good interface is what turns a working system into a used system.

Do you build mobile interfaces too?

Yes. The web applications I build are responsive and designed to work properly on mobile, not just to survive being resized.