The Restaurant and the Kitchen

There is a big difference between getting something made for you and building something that is truly yours.

Imagine walking into a restaurant and ordering a meal. You tell them what you want, and they bring you food. It may be good. It may even be close to what you asked for. But the restaurant still made most of the real decisions. They chose the ingredients they had on hand. They decided how the plate would look. They controlled the seasoning, the portions, the texture, and the final taste.

Now imagine a different experience.

You still have help, but this time you are in the kitchen. You choose the ingredients. You decide what belongs in the recipe and what does not. You taste as you go. You adjust the seasoning. You decide how it should look, what it should feel like, and what kind of reaction you want someone to have when they experience it.

That second experience feels different.

It feels personal. It feels intentional. It feels like ownership.

That is the difference between simply asking AI to make something for you and learning how to build with AI while staying in control.

A lot of people today are walking into the AI restaurant, placing an order, and accepting whatever comes out. They tell a tool to build the app, generate the code, create the design, write the copy, and then they publish something they barely understand. It can look impressive at first. But when something breaks, when a customer wants changes, or when the product starts growing, they realize they never really owned the process.

This book is built on a different belief:

AI should help you build faster, not think for you. AI should support your vision, not replace it. AI can be your assistant, but you must remain the driver.

That is what this book is about.

Not hype. Not fake passive-income fantasy. Not pretending you can type one prompt and retire next month.

This is about learning how to use AI as a serious leverage tool to turn an idea into a real product, a real brand, and real income while still owning the thinking, the decisions, and the outcome.

The Tuesday My Camera Roll Broke Me

I want to tell you a story about how this book really started.

It was a Tuesday. I was trying to send a screenshot to a friend, just a dumb meme I had saved three months earlier, and I could not find it. I scrolled past forty-seven variations of the same selfie. I scrolled past a screenshot of a parking meter I did not remember paying. I scrolled past a video of a sunset that was probably beautiful but now just felt like a stranger. I kept scrolling. My thumb started to ache. My phone said 14,823 photos. I closed the Photos app and opened Instagram instead.

That was the moment I had the idea for MemeScanr, the iOS app I would eventually ship as a solo builder under my own brand, Afia Labs.

Not the pitch. Not the plan. Not the monetization strategy.

Just the feeling:

my phone is full of things I do not remember saving and will never look at again, and it is making me feel like a bad tenant in my own life.

I thought about it for three weeks before I told anyone. Then I googled “photo cleaner apps” and found four hundred of them. I almost stopped right there.

Because that is what we do, right?

We see the crowded shelf and assume there is no room for one more thing. Especially one more thing made by us.

But I noticed something. Every single one of those four hundred apps looked exactly the same. Grid view. Bulk select. Delete button. They all promised to “clean up your gallery” in the same utilitarian voice. None of them made me laugh. None of them made me feel seen. All of them made cleanup feel like a chore you owed your phone, not a thing you might actually enjoy doing on a Saturday morning.

So I started building.

I have a master’s in information systems, but I had never shipped a production iOS app. I had never built a real consumer product under my own name. I was not what the internet thinks of when it pictures an “indie iOS developer.” I had not spent years grinding on Swift. I was not a veteran of the App Store charts. I did not have a cofounder, a VC, or a design partner.

What I had was an itch, a laptop, a background in systems thinking, and a willingness to use AI tools like a master driver instead of a passenger.

Four months later, MemeScanr is in the App Store. It has duplicate detection, Memory Lane, Gallery Wrapped, Phone Therapist, a Face ID private vault called Backroom, Boost compression, seasonal app icons, and a voice that reads like your favorite group chat. All of it runs on-device. No server. No uploads.

It could have been faster. But this was my first app, and I was learning from scratch. Every week had a lesson I did not know I needed. The four months were not slow. They were honest.

I did not build it alone. I built it with AI. And the gap between what people say building with AI feels like and what it actually feels like is one of the biggest opportunities in this whole category.

What This Book Is, and What It Is Not

There are two kinds of books about building apps with AI right now.

The first kind is theory. It is written by people who have read a lot of tweets, watched a lot of demo videos, and never actually shipped a consumer product under their own name. You can tell because the advice is always clean.

“Prompt the AI to generate your backend. Then prompt it to generate your frontend. Then prompt it to generate your monetization. Now launch.”

The book ends before anything hard happens.

The second kind is success porn. It is written by someone who shipped one thing, made money, and is now selling you the shape of their victory. The stories are polished. The challenges are neatly resolved. The code is pristine. The launch was a thunderclap. You close the book inspired and somehow more paralyzed than when you started, because now you are comparing your messy first draft to someone else’s curated highlight reel.

I did not want to write either of those.

I wanted to write the book I wish I had when I was staring at an empty VS Code window at 11 p.m. on a Sunday, asking an AI agent a question I could not even phrase correctly, then watching it confidently hallucinate a fix that broke three other things.

I wanted to write about what it felt like the day Apple rejected my build for the first time.

I wanted to write about the two-day period when I thought the app was done and then realized I had built the entire vault feature on top of a trust bug that could have earned me a first review that said, “this app tricked me.”

I wanted to write about the real stuff, because the real stuff is where the teachable lessons live.

And I wanted to write in a voice that feels like a friend. Not a textbook. Not a guru. Not a LinkedIn post. A friend who has actually done the thing and is willing to tell you about the part where she cried.

The Premise You Need to Accept Before We Start

Here is the thing you have to buy into for any of this to work:

You can ship a real app, for real users, that makes real money, as a solo builder, using AI tools, but only if you stay in the driver’s seat the entire time.

Real app, real users, real money, real ownership. No cofounder, no VC, no fantasy that one prompt becomes a product. If you want easy, you are in the wrong store.

If you do buy that premise, even reluctantly, keep reading. By the end you will have a clearer sense of how to build apps with AI, and a clearer sense of who you need to become to do it well.

Because this is not only about apps. It is about agency, ownership, and becoming the kind of builder who turns ideas into assets again and again.

> Think Before You Move On

What itch have you been scrolling past? Not the one you think you should build. The one you cannot stop noticing.