Your route · 0 of 17 done

The thirty-second app

By the end of this step you'll see every app as the front of something much bigger, and know the five layers underneath.

You open the Amazon app, tap "Buy now", and close it. Thirty seconds.

Two days later, a box is at your door.

So what did you actually use: the app, or the thing behind it?

Think about what happened in those two days. Someone checked the item was in stock. A warehouse picked it. A payment cleared. A route got planned. A driver got a stop added to their day. If it went wrong, a support agent would have seen your order history before you finished typing.

The app did one job: it let you ask. Everything else did the work.

A lending platform isn't a website

Same idea, different business. A lending platform has a website with a loan form. Nice form. But the form isn't the product.

The product is everything the form triggers: checking who you are, scoring the risk, paying the money out, tracking repayments, chasing late ones, reporting to the regulator. Take the website away and you can rebuild it in a week. Take the lending engine away and there's no business.

The app is where people touch the system. The system underneath does the real work.

The five layers under every app

LayerWhat it isAn everyday example
AppsWhat people clickA shop's website, a phone app
DataWhat the business knowsOrders, customers, products, kept in databases
IntegrationsHow tools talk to each otherThe shop tells the delivery company about a new order
Jobs and automationsThings that run without anyone clickingA nightly report, a rule that sorts support emails
People and processesWho does what, and howSupport answers tickets; finance chases unpaid invoices

Most developers live in the top layer. A systems person can see all five, and knows which one a problem really lives in. When a customer says "the app is wrong", the cause is very often in a layer below.

Why this matters now

AI writes the top layer fast. Screens, forms, buttons: cheap.

The other four layers are messy, different in every business, and full of things nobody wrote down. That's where your value is now. Not "can you build an app?" but "can you see the whole thing, and make it work?"

That's the shift this course is about.

Your turn

Pick an app you used today (a food delivery app, your bank, a taxi app). Write down one thing in each of the five layers that must exist behind it for your tap to work.

    Next: Day one at Ridgeline