Chapter 3: Designing for People – Experience, Interface, and Accessibility

Designing for People 🎨

Experience, Interface, and Accessibility

Here is an uncomfortable truth for anyone who wants to build apps: users do not care how hard you worked. They don’t see your clever code or your clean architecture. They see a screen, and within seconds they decide whether your app feels good or feels frustrating. If it confuses them, they delete it and move on — there are millions of others.

This is why design isn’t decoration you add at the end. It’s the difference between an app people love and an app people abandon. A brilliant idea wrapped in a confusing interface will fail, while a simple idea with a delightful, intuitive design can win millions of users. Some of the most valuable companies in the world got that way largely because their apps were easier and more pleasant to use than the competition’s.

In this chapter you’ll learn to think like a designer — to see apps through the eyes of the person using them, to design for everyone including people with disabilities, and to judge good design from bad with a critical, evidence-based eye.

3.1 — Designing for a Thousand Different Screens 📐

The first challenge in mobile design is that there is no single “phone.” Your app might run on a tiny budget phone, a giant flagship, a foldable, a tablet, or a watch — with dozens of screen sizes, different operating systems, and users holding their devices in portrait or landscape. Designing something that works well across all of them is a real art.

User Experience vs. User Interface

Two terms sit at the heart of design, and people often mix them up:

User Experience (UX) is the whole journey — how easy, fast, and satisfying it is to actually get something done. Good UX means a user can accomplish their goal without frustration.
User Interface (UI) is the visible surface — the buttons, colors, icons, text, and layout the user sees and touches.

A helpful way to remember the difference: if an app were a restaurant, the UI is the menu design, the plates, and the decor, while the UX is whether you had a good meal, got served quickly, and left happy. You need both. A beautiful UI can’t rescue a miserable experience, and a smooth experience still needs a clear, attractive interface.

Responsive Design

The main tool for handling all those different screens is responsive design — building layouts that automatically rearrange themselves to fit whatever screen they land on. Instead of designing one fixed layout, designers create flexible ones: elements grow, shrink, stack, or reflow so the app feels right on a small phone and a large tablet alike. Modern frameworks like SwiftUI and Jetpack Compose are built around making this kind of adaptable layout easier.

3.2 — The Principles of Interface Design 🧭

Good interfaces aren’t magic or pure “talent” — they follow principles that designers have refined over decades. Here are the ones that matter most.

Make It Intuitive

An intuitive design app is one people can figure out without a manual. This works by matching users’ existing expectations: a button looks tappable, a magnifying glass icon means search, swiping down refreshes the page, and the back arrow goes back. When you follow these shared conventions, users feel instantly at home. When you break them for no reason, you force people to stop and think — and thinking feels like work.

Make Common Tasks Easy

Every app has a few things users do constantly and a few they do rarely. A core principle is that the most common tasks should be the easiest to reach. If people open your messaging app mainly to send a message, the “new message” button should be big, obvious, and reachable with one thumb. Buried, tiny, or hidden controls for frequent actions are a classic design failure. Designers think hard about the “happy path” — the main journey most users take — and make it as smooth as possible.

Design for Users With Disabilities

This principle is one of the most important, and the most overlooked. accessibility means designing so that people with disabilities can use your app fully. Consider:

People who are blind or have low vision rely on screen readers that read the interface aloud — so every button and image needs a text description.
People who are colorblind can’t rely on color alone — so an app shouldn’t signal “error” with only a red color; it needs an icon or text too.
People who are deaf or hard of hearing need captions for any audio or video.
People with limited motor control need buttons large enough to tap reliably and gestures that aren’t too precise.

Designers use guidelines like the Web Content Accessibility Guidelines (WCAG), and both Apple and Google build powerful accessibility tools into their platforms. Here’s the key insight: accessible design usually makes the app better for everyone. Captions help someone watching a video on a loud bus. Big buttons help someone using their phone in the cold. Designing for the edges improves the middle.

Handle Errors Gracefully

Users will make mistakes — tap the wrong thing, lose their connection, type an invalid password. Good design plans for this. Instead of a cryptic “Error 403,” a well-designed app says, in plain language, what went wrong and how to fix it: “No internet connection — check your Wi-Fi and try again.” Great apps also prevent errors before they happen (graying out a button until a form is complete) and give clear, immediate feedback so users always know what’s going on.

3.3 — Judging Good Design From Bad 🔎

Being able to critique design is a skill in itself — and one the standards specifically ask you to develop. Professionals evaluate interfaces against consistent criteria, rather than just saying “I like it” or “I don’t.”

The Criteria of Usability

When you evaluate an app’s interface, look at each of these:

Criterion	Questions to Ask
Navigation	Can you always tell where you are and how to get back? Is it easy to move around?
User input	Is typing and entering information quick and painless? Are there shortcuts?
Gestures	Are swipes, taps, and pinches natural and consistent with the rest of the phone?
Orientation	Does the app work well in both portrait and landscape (when appropriate)?
Communication	Are alerts, confirmations, and feedback clear, timely, and not annoying?
First impression / polish	Does the app look finished and trustworthy, or rough and buggy?
Launch time	Does it open quickly, or make you wait and stare at a loading screen?

How Design Shapes Feeling

The stakes here are higher than they seem, because design directly controls how a user feels. An app that responds instantly, guides you smoothly, and looks polished makes you feel capable and calm. An app that’s slow, confusing, and cluttered makes you feel frustrated and even a little foolish — and that feeling attaches itself to the whole product. Designers talk about apps that “motivate” users (making them want to continue) versus ones that “demotivate” them (making them want to quit). Every slow load, mystery button, and unexplained error is a small push toward the exit.

Comparing Apps

One of the best ways to learn design is to put two apps that do the same thing side by side and compare their usability against the criteria above. Why is one weather app a joy and another a chore, when both just show you the forecast? Usually the answer isn’t the data — it’s the design. Learning to spot exactly why one feels better trains your eye to build better apps yourself.

Chapter 3 Activity: The Usability Showdown 🔍

You’re going to become a professional design critic, using real criteria to evaluate real apps — the exact skill the standards call for.

Part 1: Pick Your Contenders

Choose two apps that do the same basic thing — two weather apps, two note-taking apps, two music players, two food-ordering apps. They should be genuine competitors so the comparison is fair.

Part 2: Score Them

Create a comparison chart. Down the side, list the seven usability criteria from Section 3.3 (navigation, input, gestures, orientation, communication, polish, launch time). Across the top, put your two apps. For each criterion, give each app a score from 1 to 5 and write one sentence of evidence justifying the score — a specific thing you observed, not just a feeling.

Part 3: Judge Accessibility

Add an eighth row: accessibility. Test each app with at least one accessibility check — turn on the screen reader, check whether it supports larger text, or see whether it relies on color alone to communicate. Note what you find.

Part 4: Deliver the Verdict

In a short paragraph, declare which app has the better overall design and defend your verdict with specific evidence from your chart. Then describe one concrete change that would most improve the losing app — and explain, using the ideas of “motivate” and “demotivate,” why it would help.