A web application is software that runs in the browser, knows who you are, and changes state when you act. The six famous examples below each demonstrate a pattern the industry copies. The six after them I built and shipped myself, which means I can tell you what each pattern costs and where it bites.
Six famous examples, by pattern
| App | Pattern it demonstrates | What to notice |
|---|---|---|
| Gmail | The app-in-a-browser | Proved a browser tab could replace installed software for something as constant as email |
| Google Docs | Realtime collaboration | Two cursors in one document. Sync is the product, not a feature |
| Figma | Heavy tooling in a tab | A full design suite in the browser, where "install nothing" beat a desktop incumbent |
| Notion | The flexible workspace | One data model (blocks) wearing a hundred faces: docs, tables, wikis, kanban |
| Trello | One metaphor, done well | Cards on boards. Scope discipline as a product strategy |
| Shopify admin | The operational backend | The public store is a website. The admin running it is the application |
Notice what all six share: accounts, stored data, and actions with consequences. That is the working definition, and I unpack it properly in web application vs website.
Six I built and shipped
These are live products, not mockups. Three have public case studies you can read.
1. A multi-tenant CRM
Pipelines, contacts, tasks, billing, a page builder, and AI agents that act on records. The pattern is the classic business web app: many companies on one codebase, each seeing only its own data. Multi-tenancy is also the single hardest thing to retrofit, which is why it has to be a day-one decision. Case study here.
2. A realtime app for two people
Realtime sync, shared lists, video, and games for two people on different devices. The pattern is the realtime app, the same family as Google Docs: the hard part is not the features, it is keeping two clients agreeing about state. Case study here.
3. A client portal
Files, progress, updates, and approvals in one logged-in place, plus a browser extension for pinning feedback onto a live page. The pattern is the client portal, the most requested web app in small-business work, because it replaces the "any update?" email. Case study here.
4. Cookieless analytics
A tracking script, an ingestion endpoint, and a dashboard answering "how is my traffic" across roughly 20 sites without cookies. The pattern is the data pipeline app: the UI is the easy half, and the write path that must never lose an event is the real build.
5. A trends dashboard
Aggregates trend data into a browsable, searchable dashboard with audio summaries. The pattern is the read-heavy dashboard: ingest on a schedule, cache aggressively, and make the reading experience fast enough that people come back.
6. An SEO rank tracker
Tracks keyword rankings, runs site audits, and prices every recommendation with live search data. I built it because I wanted the tool, and this article exists partly because its keyword data said it should. The pattern is the API-orchestration app: most of the product is talking to other services well, with caching and cost control doing the quiet work.
What the examples add up to
- Every business web app is one of a few shapes. Portal, dashboard, CRM, pipeline, tracker. Vendors dress them up, but the underlying patterns repeat, which is why an experienced builder can scope them quickly.
- The visible screen is the small half. Across all six of mine, the auth, permissions, data model, and admin surfaces outweighed the pages users praise. Budget accordingly, and my cost breakdown shows exactly where that money goes.
- Browser-first keeps getting stronger. Everything above ships to every device instantly, with no app store between you and your users. For most business software the web is not the compromise option, it is the correct one.
More of my shipped work, including the client builds, is on the work page. If one of these patterns looks like your problem, custom web app development explains how a build with me runs, or just describe the workflow you want to kill.
FAQ
Is Gmail a web application?
Yes, and it is probably the one that taught the world what a web app is. It runs in a browser, knows who you are, stores your data, and performs actions with consequences. If someone asks what a web application is, "Gmail, but for your problem" is often the fastest honest answer.
What is the difference between a web app and a website?
A website publishes the same content to everyone. A web application has accounts, stores data, and changes state when users act. Most real projects pair one of each: a public site that explains and ranks, and an application behind a login that does the work. I keep a full comparison at web application vs website.
What web apps do small businesses actually need?
The same three shapes, over and over: a client portal so customers stop emailing for updates, an internal dashboard that replaces the Monday spreadsheet ritual, and a CRM shaped like the actual sales process. Almost every request I get is one of those wearing different clothes.
Do web apps work on phones?
Yes. A well-built web app is responsive by default and can be installed to the home screen as a PWA, with push notifications where they are supported. Several of the apps I run daily live on phones without ever touching an app store.