Web applications
Web development: applications, not brochure sites
Customer portals, dashboards, booking systems and internal tools — server-rendered, written in Dart, without the framework sprawl nobody wants to maintain four years later. Fixed price per written scope.
Fixed price per written scope (€60/h equivalent)
I build web applications with Jaspr: customer portals, dashboards, booking systems and internal tools — server-rendered, written in Dart, without the framework sprawl nobody wants to maintain four years later. Fixed price per written scope.
When this fits#
- Customer portals and login areas: your customers see their orders, documents or readings — cleanly separated by role.
- Internal tools: the process that lives in Excel and e-mail becomes an application with real data and validation rules.
- Booking and administration: appointments, resources, orders — with status logic that is guesswork in a spreadsheet.
- The step after a prototype sprint: the prototyped process becomes the production web application.
Why server-side rendering#
- Faster first paint: the browser receives finished HTML; the page is visible before JavaScript starts — also on older devices.
- Robust without JavaScript: forms, navigation and content work when scripts are blocked.
- Privacy-friendly by construction: this website itself is built that way — server-side rendering, self-hosted fonts, no gate in front of content. The same technology goes into your application.
- One stack, one language: Dart in the browser and on the server — the same types, the same models, no translation layer between frontend and backend.
How a project runs#
The mechanism is the same as for all my offers: written scope with testable acceptance criteria, fixed price (computed at a €60/h equivalent, never open hourly), weekly deliverable states, written acceptance, handover of repository, documentation and CI. Details: /en/prozess.
Together with the backend: for applications with their own data storage I build the Serverpod backend alongside — data models, interfaces, roles and permissions from one hand.
Reference#
For AstraCaB GmbH in Munich I co-built the booking website of a transport platform (React) and built its driver app in Flutter — production work inside an existing system stack. This very website serves as the reference for the Jaspr stack: server-rendered, no tracking before consent.
After acceptance#
Build-out (€480/day) for further changes, maintenance & operations (€240/month) for hosting, updates, monitoring and small monthly changes — or you run the application with your own team. The code is yours.
Next step#
Free 20-minute intro call — or describe your project in three minutes by e-mail, phone (+49 156 79817895) or WhatsApp.