The Button That Started Everything

The Button That Started Everything

Maya Chen was seventeen years old, and on the night before the hackathon, she hated every button on her phone.

Not the buttons themselves, exactly. Buttons were fine. Buttons were everywhere — in elevators, on remotes, on her microwave. Buttons were the duct tape of the modern world, holding everything together with small, clickable compromise. What she hated was the *feeling* of them. The feeling of being asked, over and over, in the same flat little tone: *What do you want? Pick from this list. We dare you to want something we didn't predict.*

She was sitting cross-legged on her bedroom floor, the door half shut, the hallway light off so her parents would think she'd gone to bed. Her journal — a real one, a moleskine with a cracked spine she'd carried since middle school — was open on the carpet in front of her. Above the journal, propped against the leg of her desk, was a printout of the hackathon brief. She'd read it so many times the corners were soft.

Design a study companion for high schoolers that feels less like an app and more like a friend.

Underneath, in small type, the judges had added: *Bonus points for using emerging AI capabilities in a way that doesn't feel intrusive.*

Maya had stared at the word *intrusive* for ten minutes before she got up to find a pen. Now she was writing, but not about the brief. She was writing about buttons. Specifically, she was trying to answer a question that had been itching at her for weeks:

*If my phone can recognize my face, my voice, the songs I'm humming, the route I walk to school, and the exact moment I usually open Instagram — why does it still need me to tap "Save"?*

She drew a small floppy disk in the margin of her journal. Then she drew a cross through it. Then she underlined the crossed-out floppy disk three times and wrote, in the dramatic handwriting she used when she was angry: WHO DECIDED THIS.

The floppy disk had been obsolete for at least a decade, maybe longer. Everyone knew that. But the little square icon that meant *save* was still a floppy disk on most apps, the same way the magnifying glass still meant *search*, the same way the little house still meant *home*, the same way the gear still meant *settings*. The icons were fossils. They were the bones of old ideas that nobody had bothered to bury, and every day millions of people tapped them without thinking, the way you tap your foot to a song you've heard ten thousand times.

Maya was tired of tapping without thinking. She was tired of the grid.

She flipped back a page in her journal. There, sketched in soft pencil, was a drawing of the home screen of her favorite game when she was nine years old. It was called *Cloudberry Kingdom*, and it had been a side-scrolling platformer with no menus, no tutorials, no pop-ups. You just pressed *Start* and the world unfolded. When you died, you came back. When you won, there was a tiny animation and then the next level. The whole thing felt less like software and more like a place. Maya used to lie on the carpet with her brother and pass the controller back and forth for hours. They never read a manual. They never looked anything up.

She touched the sketch with her fingertip.

Then, with the kind of determination that only happens at 11:47 p.m. on a Friday, she took a red pen and drew an X through the sketch.

---

The Sketch and the Splinter

What Maya was doing, without knowing the words for it yet, was *tearing an interface apart* — not to break it, but to see how it had been glued together in the first place.

She started with her old game. She wrote a list:

Things it had:

• A character you controlled directly
• Physics that responded to your input in real time
• Levels that got harder gradually
• Death, but no punishment for dying
• A clear sense of progress without a progress bar

Things it didn't have:

• A settings menu
• A save button
• A login screen
• A "share to social" prompt
• A tutorial pop-up
• A subscription page
• An ad

She stared at the second list. It was longer than she expected.

Now she made a different list. She opened three of the apps she used most — a notes app, a calendar app, and a music app — and listed their buttons. She didn't draw the icons. She wrote what the buttons *did*:

• A floppy disk → "save what I just wrote"
• A right-pointing arrow → "send this to someone"
• A plus sign → "add a new thing"
• A trash can → "delete this thing forever"
• A gear → "open seventeen more options, four of which I understand"
• A magnifying glass → "search for something in a giant list I can't see"

Then she wrote the question underneath, slowly, because she wanted it to be exactly right:

> Every one of these buttons is the app admitting it doesn't know what I want. Why is that considered a feature?

That was the splinter. It was small, and it didn't hurt yet. But it was in.

The next morning, Maya carried her journal to the hackathon and pushed it across a folding table to her teammates, Devi and Lucas. Devi was a senior who could code circles around most of the people in the building. Lucas was a junior who had, against all odds, taken a psychology elective and remembered most of it. The three of them had been a team since sophomore year, when they'd accidentally won a robotics competition with a robot that mostly just bumped into things politely.

Maya didn't know it yet, but the next 48 hours were going to change her life in the way that a really good book changes a person — not all at once, but chapter by chapter, until one day you realize you're thinking differently and you can't remember exactly when it started.

Devi read Maya's list. Lucas read it twice. Then Devi looked up.

"Are you saying we should delete all the buttons?"

"I'm saying," Maya said carefully, "that I want to know *who decided*. And I want to know *why we stopped asking*."

Lucas tapped the page. "This is the kind of question that gets people tenure."

"Good thing we don't have tenure," Maya said. "We have thirty-six hours and a bag of Sour Patch Kids."

The team laughed, and then, because it was a hackathon and there was no time to waste, they got to work.

But before they did, Maya asked them to do one thing.

"Today," she said, "I want every one of us to keep a button journal."

Devi raised an eyebrow. "A what?"

"Every button we tap. Every tap we wish we didn't have to make. Every moment we wanted the app to just *know* what we meant. We write it down. By tomorrow morning, we'll have a hundred little stories about what's broken. And then we'll fix at least one of them."

Lucas grinned. "Spoken like a true UX researcher."

Maya shrugged. "I don't know what UX means yet. But I'm about to find out."

---

A Short History of Things That Made Other Things Easier

The story of the button is the story of computing itself, and like most stories about computers, it begins in a small room full of people who were trying to make life less annoying.

Before graphical user interfaces — GUIs — there were command lines. You typed a word, the computer did something. If you typed the wrong word, the computer did nothing, or worse, did something you didn't want. Most people never touched a computer because learning to use one felt like learning a private language spoken by people who didn't want you to join the conversation.

In the late 1960s and early 1970s, a team of researchers at a place called Xerox PARC — a research lab in Palo Alto, California — began to ask a different question. What if computers didn't require you to memorize commands? What if they showed you pictures of what they could do, and you pointed at the picture? In 1973, they built a machine called the Xerox Alto. It had a screen, a mouse, and windows that opened and closed. You could move files by dragging little icons of them, the way you'd move a piece of paper on your desk. It was, by all accounts, magical.

Steve Jobs visited Xerox PARC in 1979. He saw the Alto. H