Web Applications
Most business applications belong in the browser: nothing to install, reachable everywhere, updated centrally. I build them as standalone applications with their own data, not as a surface on top of someone else's system.
A capability is a means. The linked areas describe what it is used for.
What specifically gets built.
Every line is a commitment about future work — none of it is a claim about completed projects.
The decisions behind it.
Categories rather than vendor names — which product is used depends on your existing systems.
- One type-checked language throughout, server and client
- Pages are assembled on the server — which shortens load times, even with large lists
- Relational data storage where the process calls for it
- Access control is planned at the data layer, not only in the interface
What is not included.
So that no time in the intro call is spent on an expectation I do not meet anyway.
- No page-builder or no-code platform
- No customising of an existing off-the-shelf product
- No visual design without function
These eight capabilities are means, not offerings. Which of them are used follows from the process — not the other way round. If you are not sure which ones you need, that is the normal case and not a problem.