←BaldanAll skillsLet's talk

Skill 05 · Web, SaaS & Mobile

Products people log into every day.

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.

Next.jsReactTypeScriptFastAPIPostgreSQLExpoReact NativeCloud Run
Open the web lab

One app, every screen

The same product, wherever people are.

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

Jakarta Air
OverviewForecastAlertsSettings
PM2.5 now…µg/m³
Temperature…°C
Wind…km/h
PM2.5, last 24 hours
Next hours (CAMS forecast)…

Live data: Open-Meteo (CAMS air quality and weather, CC BY 4.0).

Three ways to ship a product

Web, SaaS and mobile, in one minute.

They overlap more than the names suggest: most SaaS products are a web app plus mobile apps, sold by subscription, on one backend.

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

Next.jsReactVueLaravel

02

SaaS

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

Accounts & rolesTenantsBillingPlans

03

Mobile app

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

React NativeExpoFlutterKotlin

Anatomy of a modern app

Five layers and a few services.

Every product here, from a landing page to a banking app, is some version of this stack. Click a layer.

Interface01API02Business logic03Data04Infrastructure05request ↓↑ responseAuthPaymentsNotificationsObservability

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

Next.jsI useExpressI useFastAPII useLaravelGoI use
Concepts for this layer →

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

What happens in the second after you click.

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.

Your page load · measuring…/skills/web-mobileserver / CDNthis page, as filesWeb, SaaS& MobileOpen →one click → one requestGET /skills/web-mobileyour cacheresolverroot & .comname serverthis site → which IP address?measuring…youserverSYNSYN-ACKACKClientHelloServerHello + certificateFinished · keys agreedTCP · agree to talkTLS · agree on encryption keysmeasuring…request (simplified)GET /skills/web-mobileHost: this siteAccept: text/htmlAccept-Encoding: br, gzipresponse (real, asked again just now)asking…measuring…HTMLmeasuring…CSSmeasuring…Fontsmeasuring…JavaScriptmeasuring…Imagesmeasuring…Data (API)measuring…Othermeasuring……each square ≈ 1/96 of the bytesHTML → DOM treeCSS → stylesLayout: wherePaint: pixelsmeasuring…JavaScript wakes it upclicks, menus, animationsattached to the painted pageamber = interactive nowready (DOMContentLoaded)…largest element painted…everything loaded…Jakarta · now…what the app downloads: real JSON, fetched just now (the part it uses)fetching…

Explore

Go deeper.