Plans d’interface en verre sombre qui s’articulent autour d’un état lumineux violet et de connexions cyan.

Product & software

Custom web application development

A web application opens in a browser, updates for everyone at once, and needs neither install nor store review. It is the shortest path from a decision to production.

Start a project See the work

Expertise: Product & software
Platform: Browser · desktop and mobile
Stack: TypeScript · React · Next.js · PostgreSQL
Scope: Scoping · interfaces · API · operations
Delivery: Continuous deployment, without downtime

01 / 06

Website, web app, or mobile app?

The useful question is not "web or native": it is whether your users work at a connected screen or on the move.

A website publishes content: you read it, browse it, fill a form. A web application does work: it holds state, accounts, rights, data that change while you watch. The line is not the technology, it is what the user comes to do.

Against mobile, the web wins on update speed, the absence of a store, and one codebase for every screen. It loses on reliable notifications, long offline use, and hardware access.

So the useful question is not "web or native" but: do your users work at a connected screen, or on the move with unreliable network? The answer decides, and it is decided at scoping.

02 / 06

What sets an application apart from a site

01
Living state
Data that change during a session, screens that must stay consistent with each other. Perceived quality is decided here: an interface that contradicts itself after an action destroys trust in a second.
02
Accounts and rights
Authentication, sessions, roles, permissions. Treated as a product feature with its error journeys, not as a box ticked at the end of the project.
03
Real time
Several people on the same document, a dashboard that moves, a notification that arrives. Useful when collaboration is real — costly when you add it by reflex.
04
Volume
A large table, filters, exports. Pagination, indexes, and virtualised rendering decide whether the tool is still usable after years of use.
05
Integration
Accounting, mail, calendar, payment, ERP. An internal app that talks to nothing recreates the double entry it was meant to remove.
06
Operations
Continuous deployment, logs, surfaced errors, backups. An application lives for years: it is designed to be taken over, not only shipped.

03 / 06

How we work

Scoping on real use, including the workarounds your teams invented.
Manipulable mockups on the screens that carry the value, before writing code.
A version usable in production early, then visible increments on a regular cadence.
A documented API and a defensible data model — that is what costs most to fix later.
Code, database, and documentation delivered: you stay free to take over or change vendor.

Proof in context

See the work behind this expertise

Product, architecture, and operations choices, explained on real studio projects.

Case studyStellaryThe command post for teams that ship with AI agents. You describe a project, the agents move it forward under explicit rules, and a human keeps hold of what matters. Open beta.Product, design and development

05 / 06

What we get asked most

The answers we give anyway at the first conversation.

How is this different from business software?

The format, not the craft. "Web application" describes how you reach it — a browser; "custom software" describes the use — an internal tool built on your processes. Most of the business software we build is, in fact, a web application.

Can it be used offline?

Partly: an installable web app keeps what it has already loaded and syncs when the network returns. For lasting field use offline, a mobile application remains a better fit.

How do you handle load?

By measurement, not decorative anticipation. Indexes and queries held from the start, then observation of real use. Over-sizing an application that will never pass a small user base is a pure cost.

What if the application must become a product we sell?

That is the move to a SaaS: customer isolation, subscriptions, administration. Better to know it at scoping — a few architecture decisions change, and they are hard to retrofit.