Hey App, Wake Up — The World Just Changed and Nobody Told You

Hey App, Wake Up — The World Just Changed and Nobody Told You

It was November 2022 and I was on my couch in the worst mood. I'd just spent two hours fighting with my bank's mobile app trying to dispute a charge, and I'd finally given up and called the phone number like it was 2005. While I waited on hold, listening to soft jazz and a recorded voice telling me my call was important, I did the thing I always do when I'm annoyed: I opened ChatGPT, mostly to complain about my bank to a chatbot that didn't care.

I typed something like, "Why is every app so stupid?"

And then it answered me.

Not with a customer service script. Not with "I'm sorry to hear that, please hold." It said something close to, "That sounds frustrating. Apps often feel rigid because they were designed for predictable tasks. Can you tell me more about what you were trying to do?" And then it kept asking me good questions, and I kept answering, and by the time the actual bank person finally picked up the phone, I'd already figured out what was going on with my account. Not because the AI solved my problem for me. Because it helped me think.

I hung up on the bank person (sorry, Karen) and I had this very strange feeling. The same feeling I get when I watch a movie from the 1990s and everyone is using a flip phone. Everything around me suddenly felt... old. My bank's app. My notes app. My email. Even my smart speaker, which I realized in that moment was basically a parrot with a vocabulary.

That was the moment I knew something had shifted. Not just in AI. In how we relate to software. In what an "app" even means. And I want to start this book there because if you've ever had a moment where a piece of software felt less like a tool and more like a person, you've already felt the earthquake. You just don't know its name yet.

The name is this: software is waking up.

Not becoming sentient. Not getting a soul. But shifting from a vending machine to something closer to a friend. And that shift is going to redesign every app you've ever used, every job you've ever thought about, and probably a few industries you didn't even know were industries.

This book is about how to design for that shift. And the wild part? You, the teenager reading this, might be the most qualified person in the room to do it. More on that in a bit. First, let's set the stage.

The Moment Everything Felt Old

Every paradigm shift has a "before" and an "after," and somebody always has a story about the exact minute the world changed for them. The Wright brothers have the beach at Kitty Hawk. Steve Jobs has the moment he saw the graphical interface at Xerox PARC. I have a couch and a chatbot, which is a less cinematic origin story, but it's mine.

Here's what happened in my head in the weeks after that couch moment. I started noticing how many of my apps felt broken in a way I couldn't quite name. Not "the app crashed" broken. More like... they were all playing a game I was tired of playing.

Let me explain. Most apps work like this: you learn a specific set of moves, and if you make those moves in the right order, you get what you want. Want to send a photo to your friend? Open Photos, tap Share, tap Messages, pick your friend, tap Send. Want to split a bill? Open Venmo, tap Pay or Request, type the amount, add a note, hit Pay. There are buttons. There are menus. There is a small number of legal moves, and you must pick one.

This works! It's not bad design. It's just... constrained. The app knows a finite set of things it can do, and your job is to figure out which one you want. Designers in the 2010s called this "discoverability," and they got very good at it. They built menus and breadcrumbs and tooltips and onboarding tutorials and hamburger icons and tab bars and a thousand tiny affordances to help you find the right button in the right menu in the right order. And for the apps of that era, this was genuinely great design.

But then I started using AI tools. First ChatGPT, then GitHub Copilot because I'm a programmer, then Notion AI because I'm a writer who can never finish anything, then a thing called Perplexity because someone on the internet told me it was better than Google. And all of these tools felt different. They didn't have buttons in the same way. They didn't have menus in the traditional sense. They had a text box. And inside that text box, anything I could type, they would try to do.

The first time I asked Notion AI, "Hey, can you take this messy meeting transcript and turn it into bullet points organized by who said what and what we agreed to do?" and it actually did it — well, mostly, OK, it made up one name, but I could fix that — I felt the floor move. Because that meeting transcript was twelve pages of garbage. The old Notion wouldn't even let me copy and paste twelve pages without choking. The new Notion read it like a person would. Or at least the way a person would if the person had infinite patience and zero opinions.

And the weirdest part? The new tools felt less like tools. They felt more like coworkers. Or interns. Or that friend who's really good at one thing but also somehow good at three other things and is happy to take direction but also, if you don't tell them what to do, will just sit there.

I started noticing how my relationship with software was changing. With my calculator, I'm a customer. I want a number, I get a number, I leave. With ChatGPT, I'm more like a project manager. I'm giving direction. I'm reviewing output. I'm saying, "no, do it this way." I'm collaborating with software in a way I never have before.

This is the shift. Software isn't just a thing you use anymore. It's a thing you work with.

And here's the part that should make every designer, every product manager, every founder, and frankly every teenager who ever made something in Roblox sit up straight: every assumption we have about how apps should look, feel, and behave is now up for grabs.

Buttons? Maybe. Maybe not. Menus? Maybe. Maybe not. Onboarding tutorials? Oh boy, those are going to get weird. The hamburger icon in the top left of every app? Probably on its way out. Status bars, breadcrumb trails, tab bars, navigation drawers — all of those things were invented for a specific kind of software. That kind of software is becoming one option among many, not the default.

This is the moment. And like any moment, it's exciting and terrifying. Mostly because nobody knows exactly what's going to happen, including me.

Why Your Calculator Can't Surprise You (And Why That Matters Now)

OK, I want to slow down and explain something that's going to come up over and over in this book, because it's the foundation of everything. The difference between deterministic software and probabilistic software. It sounds like a phrase from a graduate-level computer science class, but I promise you understand it intuitively. Let me just give it a name.

Deterministic software is the kind of software that does the exact same thing every single time, given the exact same input. If you type 2 + 2 into your iPhone calculator, you get 4. Always. If you tap the same spot on a vending machine button, you get the same bag of chips. If you open Maps and type the same address, you get the same route. Same input equals same output, every single time, in every parallel universe.

This is not a bug. This is a feature. In fact, for most of the history of computing, this has been the entire point. We built computers because they're reliable. They don't get tired. They don't have bad days. They don't, like, secretly decide to round 2 + 2 up to 5 because they're feeling chaotic. That reliability is why we trust them to fly planes and process credit cards and keep our phones working.

Every pattern, every UI convention, every design rule you've ever internalized was built for deterministic software. When a designer tells you "the user should always know what the app is going to do next," they're assuming determinism. When a r