Web development
Line-of-business web applications that replace paper and spreadsheets, usable in the field as much as at a desk. Built with current frameworks, designed around the user rather than the framework.
What we do, and what we do not
We do not build brochure websites or standard online shops. Excellent studios do that better and cheaper than we would. What we build are line-of-business applications: tools a team uses every day to do its work.
That changes everything about how you design. A website is judged on its bounce rate. A business tool is judged on how many actions it takes to record a job, and on what happens when the network drops mid-entry.
Line-of-business applications
Four families cover most of our web work. All of them share daily use by a limited number of people, for whom every second saved counts.
Field capture and tracking
Long forms, photos, signatures, location. Usable with a finger, with gloves, on a screen in full sunlight.
Dashboards
Aggregation of heterogeneous data, filters, exports. Fast even on large volumes.
Portals and client areas
Authentication, roles, documents, invoicing. Interfaced with your existing systems.
Back offices
Administration interfaces that are genuinely usable, rather than a generator dropped on top of a database.
In the field, in the browser
A well-built web application installs onto a home screen, works offline and updates itself. No app store to go through, no review to wait for, no device estate to manage.
It is often the best compromise when users work on devices they already own and you do not control. And it extends the life of existing hardware, which is not a neutral consideration.
Performance and accessibility as acceptance criteria
We set quantified thresholds at the start of the project: time to first useful content, maximum page weight, WCAG level AA conformance. Those thresholds form part of the acceptance criteria and are verified at every delivery.
Accessibility is not only a public-sector obligation. A form that can be navigated by keyboard, with sufficient contrast and explicit labels, is faster for everyone to use.
What remains after us
We favour technologies for which you will still find developers in ten years: TypeScript, React and Next.js, or Angular when your team already knows it. No obscure framework, no proprietary generator.
Hosting runs on Swiss infrastructure or at your site, with the code and the deployment pipeline in your repository. You can hand the work to another team without a rewrite.
An example
A web management platform for law firms: company incorporation, shareholder registry, general meetings and AI-assisted search across cantonal tax sources, end to end.
Frequently asked questions
Do you build brochure websites?
No, and we would rather say so immediately. Our trade is line-of-business applications and internal tools. For a presentation site or an online shop, other studios will do better and cheaper.
Web application or native mobile app?
If your users work on devices you do not control, the web almost always wins: nothing to install, nothing to deploy. If you need deep hardware access or intensive daily use, native takes the advantage back.
Can the application be used without a connection?
Yes. A progressive web app stores its data locally and synchronises on reconnection. It has to be planned from the design stage, not added afterwards.
Next.js or Angular?
Next.js by default, for the ecosystem and the performance. Angular when your internal team already knows it and will take on maintenance, which matters more than technical preference.
Do you handle hosting?
We set it up and can operate it under contract, on Swiss cloud or at your site. The account is opened in your name and the infrastructure is described as code in your repository: you can take over whenever you want.
Let's talk about your project.
Describe your need in a few lines. We answer within 48 working hours, with a first technical opinion rather than a sales pitch.