Client or partner portal
Invoices, order submission, signed document upload.
What is a web application? Definition and examples
A web application is software used in a browser with interactive screens, user accounts and server-side business logic. Unlike a mostly informational marketing site, it handles actions: open a case, approve an order, track inventory. Data persists between sessions.
In one sentence
A web application is an online business or customer tool — not just a page to read.
Key points
- It combines UI (front-end), APIs or dynamic pages and data storage.
- Authentication and roles define who sees what — critical for B2B portals.
- It can replace a shared spreadsheet or desktop tool when remote access matters.
- Performance and security matter as much as installed software: sessions, CSRF, backups.
Term at a glance
- Web application
- Web app · Webapp
- French term
- Application web
- Domain
- Web development
- Category
- Fundamentals
- Level
- Beginner to intermediate
What counts as a web application?
The distinction is behaviour, not framework: users sign in, change data that belongs to them or their organization, and expect state to be saved. A product configurator with cart, HR intranet or production dashboard all qualify.
Most modern web apps split a rich browser client from a REST or GraphQL API. That lets you evolve the UI without rewriting core logic and reuse the same API for a future mobile app.
Operating a web app means environments (dev, staging, prod), database migrations, error monitoring and recovery plans. A marketing site can survive an hour offline; an order tool usually cannot.
How is a web application built?
- 01
Model business entities
Customers, orders, projects, permissions — what is stored and who may change a confirmed order.
- 02
Prototype critical screens
Validate high-value flows (sign-in, create, search) before polishing secondary pages.
- 03
Wire integrations
Payment, ERP, transactional email — each external flow tested with realistic data.
- 04
Train and measure adoption
Short docs, launch support, usage metrics to prioritize improvements.
A concrete example
A shared-services co-op launches a portal where members submit IT tickets and track status. Members see their tickets; technicians see the full queue. Email notifications go through an API. Previously everything lived in Outlook threads: the web app centralizes history and SLAs become measurable.
Typical use cases
Internal tool
Leave management, production tracking, searchable knowledge base.
Transactional platform
Booking with payment, B2B marketplace, training registration.
Decision dashboard
Near-real-time KPIs aggregated from several data sources.
Benefits and limits
- Instant rollout to every authorized user
- Cross-platform access without app stores
- Direct hooks to cloud APIs and SaaS
- Continuous improvement without client installs
- Higher initial cost than a marketing site or simple CMS
- Needs access governance and regression testing
- Limited offline unless a PWA is designed for it
- Debt if business rules were not scoped before build
Web application or marketing site?
| Web application | Marketing site | |
|---|---|---|
| Primary goal | Run actions and persist data | Inform, persuade, rank in search |
| User accounts | Often required with roles | Rare except light member areas |
| Technical depth | API, database, automated tests | CMS, content, SEO performance |
| Maintenance | Functional fixes and security are critical | Content and plugin updates |
Impact on your business
Choosing a web application means investing in an operational asset: it shapes how staff or clients work daily. Scoped well, it removes circulating file versions and creates a shared source of truth — valuable for growing organizations that cannot afford disconnected tools.
Frequently asked
Is a web application the same as SaaS?
The web app is the technical form; SaaS is a business model (rented software, multi-tenant). Your app can be SaaS or internal-only.
Can WordPress become a web application?
Sometimes with plugins, but once logic is specific and heavy, a dedicated architecture avoids CMS performance and security ceilings.
Do you also need a mobile app?
If users are mostly at a desk, responsive web is enough. Field work (scanning, GPS, push) may need native or a well-built PWA.
Related terms
Sources and references
Unsure whether you need a site, CMS or custom application for your process?
Clarify your needs