The 3 Patterns Behind Every Product

Change the company and the interface looks completely different. The mechanism underneath is always the same three steps.

The interface never decidesA click in the browser sends an API call, and the answer back from the server decides what you're allowed to see. This is why two users on the same platform can click on their menu bar and see different settings that correlate with their permission level.
Fast things are pushedFor the things that need to happen in the moment — a chat message, a badge count, a live board — the browser opens a standing line to the server when the page loads, and the server sends each change down that line the instant it happens instead of waiting for the app to ask again every few seconds. This is why a new message can appear in your chat window a second after someone else sends it, without you clicking anything.
Slow things come back laterFor the things that take longer to finish — a payment clearing, an invoice being generated, an export being assembled — the work happens on a server and a separate message is sent back once it's done, which is what a webhook is. This is why the tick mark you see next to a payment usually turns up seconds or minutes after the click, because it arrives on that later message rather than with the click itself.

Ten Kinds of Product

Click one to see the calls behind it.

Behind the Interface

Ten separate examples, not ten steps. For each one: what you do, what quietly goes out, what comes back — then one real-shaped request and response.

1
Example 1

Social media platforms

Instagram, TikTok, X — what the end user sees: an endless feed that never seems to load

1You pull down to refresh the feed
GET /v1/feed?after=2026-10-29T09:12Z&limit=20

20 posts, already ranked, plus a cursor for the next 20

2You tap ❤️ on a post
POST /v1/posts/8842/reactions

the new like count, so the number changes before anyone else sees it

3A comment appears while you're still reading
WebSocket push {"type":"comment"}

the comment itself, with no refresh

4You post a Reel
POST /v1/uploads, then POST /v1/posts

a job id — the encoding happens in the background

2
Example 2

CRMs

Salesforce, HubSpot — what the end user sees: a contact card that seems to know everything

1You open a contact
GET /v2/contacts/ct_4821?include=owner,notes,deals

the record plus the last five activities, in one response

2You drag a deal to "Proposal"
PATCH /v2/deals/deal_77 {"stage":"proposal"}

the new board position and a recalculated forecast

3Someone fills in your website form
POST /v2/leads (from your website's backend)

a new lead card, with an assignment rule already run

4A deal is marked won
webhook → POST https://finance.example/invoices

an invoice created without anyone re-typing the order

3
Example 3

Work order management software

ServiceTitan, Jobber, Fiix — what the end user sees: a dispatch board that moves as the day moves

1You drag a job onto a technician's morning
PATCH /v1/work-orders/wo_903 {"assigneeId":"t_14"}

accepted — or a 409 conflict if that tech is already booked

2A tech taps "Start job" in the van
POST /v1/work-orders/wo_903/events {"status":"started"}

the office board turns yellow within a second

3The tech scans a part
GET /v1/inventory/sku/FLT-220

price, stock and which van it's sitting in

4The customer signs the job off
webhook → billing API + SMS API

an invoice and a payment link in the customer's texts

4
Example 4

Online calendar platforms

Google Calendar, Outlook — what the end user sees: a week view that shows other people's free time

1You open your week
GET /v1/calendars/primary/events?timeMin=...&timeMax=...

every event between Monday and Sunday, in one go

2You click an empty slot
POST /v1/calendars/primary/events

an event id, reminders and a meeting link

3A booking link checks you
GET /v1/freeBusy?ids=you@example.com

only your busy blocks — never your event titles

4Someone moves the meeting
PATCH /v1/events/evt_11, then a push webhook

your app re-fetches and the card updates itself

5
Example 5

Social networking platforms

LinkedIn, DuckBuddy — what the end user sees: suggested people, live badges, a chat that types with you

1You start typing a name in search
GET /v1/search?q=lizz&cursor= (once per pause, not per keystroke)

matches arriving as you go

2"People you may know" loads
POST /v1/graphql {"query":"suggestions"}

six people, each with a reason: same group, mutual friends

3You send a connection request
POST /v1/relationships {"to":"in_558"}

their bell badge appears instantly over a live socket

4You open a message thread
GET /v1/threads/thr_9/messages?after=

the history, then new messages pushed as they're sent

6
Example 6

Video conferencing platforms

Zoom, Google Meet, Teams — what the end user sees: a call that starts in two seconds and captions itself

1You click Join
POST /v1/meetings/mtg_77/join

a short-lived token and the server addresses your browser needs to find the other people

2You wait in the waiting room
WebSocket push {"type":"waitingRoomJoin"}

Admit / Deny appears on the host's screen

3Live captions run
audio streamed to a speech-to-text API

partial words pushed back over the socket while you speak

4The call ends
webhook → CRM, {"meetingId":"mtg_77"}

the call is logged on the contact and the recording link is emailed

7
Example 7

Payment processing platforms

Stripe, PayPal, Adyen — what the end user sees: a checkout that never asks you to leave the site

1You click Pay
POST /v1/payment_intents (from the store's server)

a client secret — the card number goes to the processor, not the store

2The processor asks your bank
webhook payment_intent.succeeded

only then does the order say Paid

3You're refunded
POST /v1/refunds {"payment_intent":"pi_3M"}

a receipt and an updated order status

4A subscription renews
monthly webhook invoice.paid

your renewal email — or a "card declined" nudge if it says invoice.payment_failed

8
Example 8

Online stores

Shopify, Amazon — what the end user sees: search, stock counts and a basket that adds up correctly

1You search "hiking socks"
GET /v1/products?query=hiking+socks&sort=relevance&page=2

20 products, a result count and a pointer to the next page

2You open a product
GET /v1/products/1841?include=variants,inventory

sizes, prices and stock per warehouse

3You add one to the basket
POST /v1/carts/items {"variantId":1841,"qty":1}

new totals plus shipping options for your postcode

4You place the order
webhook orders/create → warehouse, invoice, label APIs

a tracking number on the confirmation email

9
Example 9

Mobile apps

Strava, Uber, banking apps — what the end user sees: an app on your phone that stays up to date wherever you are

1You open the app on the bus
GET /v1/me/activities?limit=10 (from the phone app)

your last 10 workouts, sized for a small screen

2You tap Save after a run
POST /v1/activities {"type":"run","distanceM":5200}

the saved workout with its new id

3You lose signal mid-upload
the app queues the call and retries later

the workout appears once you're back online

4A friend gives you kudos
push notification from the company's server

a banner on your lock screen

10
Example 10

Smart devices (IoT)

Nest, Ecobee, Fitbit, Pelican — what the end user sees: a thermostat or tracker that reports on its own, with no one tapping anything

1Nobody does anything
POST /v1/readings every 5 minutes (from the thermostat itself)

"got it" plus any new setting to apply

2The room gets too warm
POST /v1/alerts {"type":"high_temp"}

an alert on your phone

3You change the temperature in the app
PATCH /v1/devices/t-12 {"setpoint":20}

the device picks up the change on its next check-in

4Your watch syncs after a walk
POST /v1/steps (from the tracker, via your phone)

today's step total in the app

Where to Go Next

Keep going in order, or jump to any page from the top menu.