Web app development for business applications that run in any browser
Web app development is how a company gets an application that works in any browser, on any device, without installation: a booking system, an order portal, a field reporting tool, a quoting engine, a SaaS product. We design and build custom web apps around one clear job, secure and accessible from the first release, hosted in the EU, and with the source code in your company's name.
- You see the result before it goes live
- Fixed price for the agreed scope, in writing before work starts
- Source code, domain and accounts in your company's name
What a web app is, and what it is not
A website informs: it shows mostly the same pages to every visitor. A web app works: people sign in, enter and change data, follow workflows, get results calculated for them and see their own information. Behind it are a database, business rules, permissions and integrations with the systems you already run. That makes a web application closer to software than to a website, and it is built and maintained like software. If what you need is a marketing or company site, see website development; if it is a login area for customers or partners, see website portal development.
Web apps we build
- Internal business applications: order handling, quoting, planning, approvals, case management, reporting. See internal tools.
- Customer-facing applications: configurators, booking, self-service, calculators that turn into leads.
- SaaS products: multi-tenant applications sold by subscription, with billing and administration. See SaaS development.
- Dashboards and data tools: live figures from several systems in one place. See dashboard development.
- Replacements for spreadsheets and old desktop software: the same logic, with users, permissions, history and access from anywhere.
Web app, mobile app or both?
Our web app vs native app guide covers the choice in depth, progressive web apps and store rules included.
| Need | Web app | Native mobile app |
|---|---|---|
| Used mostly at a desk, with large screens and keyboards | Best fit | Rarely needed |
| Reach everyone with a link, no installation | Yes | Requires store installation |
| Update for all users at once | Yes, on the server | Through store releases |
| Camera, location, offline use | Possible in the browser, with limits | Full access |
| Widgets, background tasks, rich notifications, watch | Limited | Yes |
Many companies start with a web app and add a mobile app for the tasks done on the move. A progressive web app can be installed to the home screen and work partly offline, which is often enough. When it is not, we build native or cross-platform apps on the same backend. Our JavaScript mobile app development guide compares the routes.
For what moves the budget of a web app, from roles and integrations to hosting and upkeep, see our guide to web app development cost; it explains the drivers without prices of our own.
Signs a web app is the right answer
- A process runs on spreadsheets and email, and errors or version confusion cost time every week.
- Customers or partners keep asking for information your team looks up by hand.
- An old desktop or in-house system works but cannot be reached from outside the office, and nobody wants to touch its code.
- A ready-made tool covers most of a process but forces workarounds in the part that makes your business different.
- You want to sell your know-how as a service to other companies.
Security built in
Web applications are reachable from the whole internet, so security is part of the design, not a final check. We build against the OWASP Top 10:2025, the awareness document for the most critical web application security risks, read on 12 November 2026. Its first entries are broken access control, security misconfiguration and software supply chain failures, which is why every web app we build has:
- access rules checked on the server for every request, per role and per record;
- sign-in with your company's identity provider or with passkeys or multi-factor authentication;
- infrastructure and configuration defined as code, reviewed and repeatable;
- dependencies tracked and updated, with automated checks for known vulnerabilities;
- logging and alerting that let you see who did what and when.
For an independent check of an existing application, see our security audit.
Roles and permissions follow the rules in your access control policy.
Accessible from the first release
Since 28 June 2025, the European Accessibility Act has covered e-commerce and several other services provided to consumers in the EU, including the websites and online applications through which they are delivered. Directive (EU) 2019/882, read on 12 November 2026, requires those to be perceivable, operable, understandable and robust. We build to WCAG 2.2 level AA as standard, for consumer and internal apps alike, because accessible apps are also faster to use for everyone. See our European Accessibility Act guide for who is in scope.
Personal data and data portability
Most web apps hold personal data, so privacy is designed in under Article 25 of the GDPR, data protection by design and by default: only the fields that are needed, retention rules, role-based access and export and deletion when a person asks. If you sell the app as a service to other businesses, the EU Data Act gives your customers switching and export rights; our EU Data Act guide explains them. We provide the material for your data protection impact assessment where one is needed.
Technology choices
We choose technology your company can live with for ten years: widely used, well documented and easy to hire for. A typical web app stack is TypeScript with React or a similar framework for the interface, a Node.js, Python or .NET backend, PostgreSQL for data, and an EU cloud region for hosting. Integrations use documented APIs, described in OpenAPI, so other systems and teams can connect; see our API documentation guide.
What you get
- A working web application in production, with the workflows, roles and integrations agreed for the first version.
- An admin view for your team to manage users, settings and content without asking us.
- Source code in your repository, with automated tests and a build pipeline that deploys on approval.
- Infrastructure defined as code in an EU cloud region, in your company's account.
- Monitoring, error tracking and backups with tested restores from the first day in production.
- Documentation: architecture, data model, API description, and how to run, update and recover the app.
- An accessibility check against WCAG 2.2 AA and a security review before launch.
How we build a web app
- Discovery. Users, workflows, data and integrations, mapped with the people who will use the app. The result is a written scope for the first version.
- Design. Clickable prototypes of the main flows, tested with real users before building.
- Build in short iterations. Working software every one or two weeks in a test environment you can use.
- Test. Automated tests for business rules, accessibility checks, and testing on the browsers and devices your users have.
- Launch. Data migration, training, go-live with monitoring in place.
- Run and improve. Updates, security patches and new features in releases.
Why our web apps last
- One clear job per app, and a first version small enough to be used in months.
- Code written for the next team as much as for this one: tests, documentation, conventional structure.
- Infrastructure as code, so environments can be rebuilt and moved.
- Measurement from the start: what the app is meant to change, and whether it does.
You own it
As a standard term, the source code sits in a repository in your company's own account, and the hosting, database and domains are in your company's name, in an EU data region. You can keep us for maintenance, run the app yourself or hand it to another team. For the wider picture, see custom software development. See prices.
Questions we get
What is a web app?
A web app is an application that runs in a web browser instead of being installed from an app store. Users sign in and work with their own data: orders, bookings, cases, reports, documents. Unlike a website, which mostly shows the same content to everyone, a web app is interactive, behind a login and connected to databases and other systems.
What is the difference between a web app and a mobile app?
A web app runs in the browser on any device, is updated once on the server for everyone, and needs no store approval. A native mobile app is installed from the App Store or Google Play and has deeper access to the device, such as background tasks, widgets and rich notifications. Many business tools start as a web app and add a mobile app only for the tasks people do on the move.
What is a progressive web app?
A progressive web app, or PWA, is a web app that can be installed to the home screen, opened in its own window and work partly offline. It suits tools used often on mobile devices that do not need features only native apps have. We decide between a PWA, a native app or both early, based on what users need.
Which technologies do you use for web app development?
We choose per project, with a bias for well-supported, widely known technology so another team can maintain the app later. Typical choices are TypeScript with React or a similar framework for the interface, a Node.js, Python or .NET backend, PostgreSQL for data and infrastructure in an EU cloud region, all defined as code.
How long does it take to build a web app?
It depends on scope. A focused first version with a few core workflows, accounts and an admin view is often in use within a few months; a larger platform grows in releases after that. We agree the first version's scope in writing, so the timeline is based on a concrete list rather than a guess.
Who owns the web app?
Your company. The source code is in a repository in your company's account, and the hosting, database and domains are in your company's name. You can keep us for maintenance, run it yourself or hand it to another team.
Get a written quote
Tell us in a few lines what you need. We reply within one working day with a written quote: scope, timeline and a fixed price or an hour estimate. Asking is free and commits you to nothing.