01
Web app
Opens in a browser: nothing to install, works on any device, and everyone gets the new version the moment it ships.
You meet it as online banking, booking sites, the tools you open in a tab
Skill 05 · Web, SaaS & Mobile
Web apps, SaaS platforms and mobile apps, and what actually happens inside them. Shown with things that run in your browser, starting with a live app and the page you are reading.
One app, every screen
A web app, a SaaS and a mobile app are mostly the same thing delivered three ways: one set of data and rules, many screens. This little app shows Jakarta's air right now, live, and re-arranges itself for each device.
a web app in the browser: wide, a sidebar, everything at once
Live data: Open-Meteo (CAMS air quality and weather, CC BY 4.0).
Three ways to ship a product
They overlap more than the names suggest: most SaaS products are a web app plus mobile apps, sold by subscription, on one backend.
01
Opens in a browser: nothing to install, works on any device, and everyone gets the new version the moment it ships.
You meet it as online banking, booking sites, the tools you open in a tab
02
A web app sold as a subscription. Many companies share one system, and each one sees only its own data, users and plan.
You meet it as accounting, HR, CRM and project tools paid per month
03
Installed from a store. It can use the camera, GPS and notifications, and keep working when the signal drops.
You meet it as ride-hailing, delivery, chat, field apps
Anatomy of a modern app
Every product here, from a landing page to a banking app, is some version of this stack. Click a layer.
A layer of the stack
API
The contract between screens and server: which requests exist and what they return.
Without it
Every screen talks to the database directly, and one change breaks them all.
Tools for this
This page, measured by your browser
waiting for the page to finish loading
…
to load this page, for you
…
files your browser fetched
…
over the network
…
until the first content
…
the protocol it spoke
…
files from your cache
Read from your browser's Performance API after the page finished loading. Nothing is sent anywhere.
Between a click and a page
One request, followed from your click to a finished page and then to a phone app. The timings are real: your browser measured this page as it loaded.
Explore
Tools
52 tools across 8 layers, the same task written in several of them, live npm downloads, head-to-heads and a stack builder.
Concepts
51 ideas in 9 groups, from HTTP, REST and CORS to JWT, multi-tenancy and offline sync, each animated; some you can run live.
Web lab
This page's live Web Vitals with experiments that break them, the real waterfall of every file it loaded, a rendering race and a responsive playground.
SaaS anatomy
A working mini SaaS with its backend exposed: sessions, tenants, roles, plans, feature flags, audit log and two languages, plus tenant isolation and unit economics.
Mobile lab
Four ways to build an app and a picker, two phones syncing offline with real conflicts, push across the app lifecycle, and your device's sensors read live.
Architectures
One shop built six ways, from monolith to microservices, serverless, static + APIs and backend-as-a-service, morphing on one canvas, with what breaks on a bad day.