What is a web app?
A web app is interactive software delivered through a browser over HTTP — it runs on a remote server, reads and writes data, and needs no app-store install.
Where a static website mostly presents information, a web app lets the visitor do something: submit a form, edit a record, run a calculation, complete a transaction. The code splits between a client (HTML, CSS, and JavaScript running in the browser) and a server (application logic plus a database). Mobile browser activity now accounts for over 59% of all web usage, so most modern web apps are mobile-first responsive — or shipped as Progressive Web Apps that install to the home screen without an app-store review.
GEO-ready
Found by Google and AI assistants
Bank-level security
SSL, automated backups, 99.9% uptime
Lighthouse 95+
Sub-second loads from the global edge
Everything included
Database, email, forms, file storage
Key points
Software you use in a browser instead of installing from an app store.
Splits into a presentation layer (browser), application layer (server), and data layer (database).
More interactive than a static website — users edit, transact, and save persistent data.
Same code runs on desktop, laptop, tablet, and phone — no separate native build needed.
Progressive Web Apps add offline support, push notifications, and home-screen install.
React powers ~40% of front-ends; Node.js powers ~42% of back-ends in 2026 surveys.
In plain language
Think of a website as a magazine and a web app as a workshop. A magazine you read; a workshop you walk into and start doing something — measuring, cutting, assembling. A web app gives you tools that respond when you click them: a search box that returns live results, a form that saves your answers, a dashboard that updates as new data arrives. Everything happens inside your browser, but most of the heavy work runs on a server somewhere else. You never installed anything from an app store; the moment you typed the URL, the app was already running. Web apps now feel close enough to native software that Twitter, Starbucks, Uber, and Tinder all ship Progressive Web App versions of their phone apps too.
Concrete examples
What this looks like in the wild — common shapes you'll recognise.
Google Docs — typing, sharing, and collaborating on a document inside the browser instead of installing Word.
Trello or Asana — drag-and-drop task boards where every action syncs to the server in real time.
Notion — a workspace that reads and writes pages, databases, and comments live inside any browser.
Figma — a vector design tool that runs entirely in WebGL with multiplayer cursors and version history.
Stripe Dashboard — a financial control plane with charts, search, exports, and webhook configuration in the browser.
Twitter Lite — a Progressive Web App under 3% of the native app's size that still pushes notifications and works on patchy 3G.
An internal admin tool a team built on a no-code platform to replace a shared spreadsheet.
Common types
The shapes this idea takes in practice — the same underlying entity, tuned to different goals.
Single-page application (SPA)
Loads one HTML shell, then renders every screen with JavaScript — fast transitions, app-like feel. Common with React, Vue, and Svelte.
Multi-page application (MPA)
Each navigation fetches a fresh HTML page from the server. Easier to index, easier for SEO, friendlier to AI assistants.
Progressive Web App (PWA)
Web app plus a manifest and service worker so the browser can install it, cache assets, and serve offline. Tinder, Starbucks, Uber all use this pattern.
Server-side rendered (SSR) app
Server assembles the HTML for each request, then hydrates with JavaScript. Best blend of fast first paint and dynamic interaction.
Static site with dynamic islands
Mostly prerendered HTML with small interactive widgets (search, cart) hydrated client-side. Common in Astro, Eleventy, and Next-style hybrids.
Anatomy of web app
The parts that make up a working version of this — what every well-built one has under the hood.
Presentation layer (client)
The HTML, CSS, and JavaScript running in the user's browser. Renders the UI, captures input, and calls APIs for data.
Application layer (server)
Business logic that authenticates requests, validates input, runs workflows, and decides what data to read or write.
Data layer (database)
Persistent storage — usually a relational database — that survives restarts, scales independently, and keeps every user's data isolated.
API surface
REST, GraphQL, or RPC endpoints (and increasingly MCP for AI agents) that let the front-end and other systems read and write data programmatically.
Authentication and sessions
Login, signup, password reset, social sign-in, and role-based access — the gate that decides which user sees and can change which data.
Hosting and edge delivery
A CDN serves static assets near the user; an origin runtime (Cloudflare Workers, AWS Lambda, container) executes server logic at every request.
Common mistakes
What goes wrong most often — and the fix that turns the mistake into a working result.
Mistake
Treating a marketing website and a web app as the same product, then bolting interactivity into a static-site generator after launch.
Fix
Pick the right surface up front: a marketing site stays content-focused; a web app starts with auth, a database, and an API on day one.
Mistake
Shipping a single-page app with no server-rendered HTML, then wondering why Google AI Overviews never cite the content.
Fix
Use server-side rendering or static prerendering for content pages; crawlers and AI assistants still parse HTML, not your JavaScript bundle.
Mistake
Skipping mobile testing because 'desktop traffic is what matters.' Over 59% of browser usage is mobile.
Fix
Design mobile-first, test on real devices, and treat sub-second mobile time-to-interactive as a launch criterion, not a stretch goal.
Mistake
Building a full native mobile app before validating the workflow on the web.
Fix
Ship a Progressive Web App first — Twitter Lite, Starbucks, and Tinder all run web versions that match or beat native on conversion and weight.
Mistake
Hiding all data behind a single internal API with no public REST surface, then exporting CSVs by hand whenever an integration arrives.
Fix
Expose a documented REST endpoint (and increasingly an MCP endpoint) for every entity; treat your own UI as one of many clients.
From concept to published app
Exepad publishes web apps end to end from a single plain-language description. The plan ships a relational database, role-based authentication, transactional email, file storage, forms with validation, edge hosting on Cloudflare with automatic SSL, a custom domain, visitor analytics, and a public REST API plus MCP endpoint. Pages render server-side with semantic HTML and JSON-LD schema, so the same app is both a Google-indexable site and a real interactive web app — Lighthouse 95+ on every page, no separate marketing-site versus web-app stack to maintain.
Frequently asked
What's the real difference between a website and a web app?+
A website is content you read; a web app is a tool you use. Most modern products are both: a marketing site visible to anyone, plus a logged-in dashboard where users do work. The distinction is mostly about interactivity and persistent data, not about the underlying URL.
How is a web app different from a mobile app?+
A web app runs in a browser and works on any device without an app-store install. A mobile app is downloaded from the App Store or Google Play and installed directly on the phone. A Progressive Web App bridges the two: web codebase, but installable to the home screen with offline support and push notifications.
What languages and frameworks are used to build web apps?+
Front-ends are HTML, CSS, and JavaScript, often through a framework — React (~40% share), Vue, Svelte, or Solid. Back-ends are typically Node.js (~42% of back-end developers), Python, Ruby, Go, or .NET, talking to a relational database like Postgres or MySQL. On a no-code app cloud, the language layer is hidden — you describe the app in any language.
Do I have to ship a Progressive Web App?+
No, but it is a low-cost upgrade for any web app. Adding a manifest and a service worker turns a normal web app into one that can be installed to the home screen, cache assets for offline use, and send push notifications — Twitter Lite, Starbucks, Tinder, and Uber all do this with measurable conversion and engagement gains.
Are web apps secure?+
When designed well, yes. SSL on every page, hashed passwords, parameterized queries, and tenant-isolated databases are baseline. Most platforms ship those defaults today. The harder work is access control — making sure each user only sees their own data — and modern frameworks and no-code platforms encode that as configuration rather than custom code.
Can a non-developer ship a real web app?+
Yes. No-code platforms and AI app clouds generate the database, the UI, and the API from a description in any language. Gartner forecasts that 80% of new technology products will be built outside traditional IT by 2026, and the majority of those will be web apps shipped without a hand-coded codebase.
How do AI assistants like ChatGPT and Google AI Overviews see a web app?+
Through the same HTML and structured data that classic search engines crawl. If a web app ships server-rendered HTML, semantic headings, JSON-LD schema, and a clean sitemap — what the industry now calls GEO-ready output — AI assistants can index its public surfaces and cite the app or its documentation directly in answers.
Build it on Exepad
Describe what you need; Exepad publishes a full-stack version with hosting, database, email, and analytics included.
Start your trial