About DEVNU

An independent practice, not a layered agency.

The person you discuss the project with is the same person designing it, writing the code and putting the release on the server.

DEVNU / OPERATING MODEL

Design and development that begin with the problem, not a template.

I built DEVNU for projects where interface, application logic and the operating environment cannot be treated as separate concerns. I first define the problem and its constraints, then take content structure, interface, APIs and infrastructure as far as that project genuinely needs. If something sits outside my scope or experience, I say so at the beginning.

Make the problem precise

Before design begins, I define what the user needs, what data enters the system and what a successful outcome actually means.

Build something tangible

Instead of extending design files indefinitely, the main path reaches the browser early enough to test with real data.

Leave the work maintainable

The repository, deployment configuration, environment variables and update steps must remain understandable after handover.

Real project evidence

A portfolio should be visible, not merely described.

Each project page explains what was delivered, what DEVNU was responsible for and where the project stands today. A direct link is included whenever a public release exists.

View the projects ↗