The Front End — the Part You Touch

Lesson 2 · taught by Pip

Hello again, friend. Pip here, light trimmed and ready. 🐙

Last time we said an app has two halves: the part you touch and the part that does the work. Today we sit with the part you touch — the front end.

What the front end actually is

The front end is everything you can see and tap. The buttons, the lists, the screens, the colors, the little spinning circle while something loads. If your finger can reach it, it lives in the front end.

Here is a plain way to picture it. Think of a restaurant. The dining room is the front end — the tables, the menu in your hands, the waiter who takes your order and brings your plate. You never walk into the kitchen. You simply ask, and food appears.

An app's front end is that dining room. Its whole job is to take what you want (your taps) and show you a clear result (your screen updating), while hiding the busy work happening out of sight.

Two terms worth knowing

People who make apps use two phrases a lot. Let me define them simply.

User interface (UI) — this is the stuff you see and touch. The actual buttons, text boxes, menus, and pictures on the screen. In the restaurant, the UI is the menu, the table, and the silverware. It is the physical layout in front of you.

User experience (UX) — this is the feeling of using it. Was it easy? Did you get lost? Did the right button sit where you expected? In the restaurant, the UX is whether you felt welcomed, found your table without confusion, and got your meal without a fuss. Same dinner, very different night, depending on the UX.

So: UI is what's there. UX is how it feels to use what's there. Good apps care about both.

Why a good one feels like nothing at all

Here is the quiet trick of a great front end: when it works well, you barely notice it.

You tap "Send," and the message just goes. You don't think about it. But behind that one tap, the app may be checking what you typed, packing it up, handing it to the back end, waiting for a reply, and refreshing the screen — all in a blink.

A good front end hides every bit of that. Like a calm waiter, it absorbs the rush in the kitchen and gives you a smooth, simple moment at the table. The more work it hides, the more effortless it feels.

A clumsy front end does the opposite. The button is hard to find, the screen freezes with no hint, you're not sure if your tap even landed. Same kitchen, same food — but a worse evening, because the dining room let you down.

So when an app feels easy, that ease is not an accident. Someone designed it on purpose, so the work stays out of your way.

Your turn

Open any app you use often. Find one button you tap without even thinking. Now ask yourself: what do you guess happens behind that tap that you never have to see?

You don't need the exact answer — just notice that something is hidden, and that the hiding is the point. That's the front end doing its job.

Next, we step through the kitchen door. In The Back End — the Part That Does the Work, we'll meet the busy half that the dining room has been politely hiding all along. 🐙