Can a non-technical person really build an app with AI?

Yes. I'm the proof, six times over. I opened Cursor for the first time in March 2025, at 49, with a career in security and zero computer science behind me. Since then I've shipped BurnoutRadar, PairHabit, and Kikko, with three more in various stages behind them. The honest version of "yes" comes with conditions, though — and the conditions are the useful part.

What "non-technical" meant in my case

When I say zero background, I mean it literally. Twenty-five years in security, not one line of code. Until March 2025 I had never opened a code editor. Nine years as a Captain in the Italian Army Special Operations Forces, then humanitarian security with the UN system across four continents — useful training for many things. Not for reading a stack trace.

What changed wasn't me. It was the tools. AI coding assistants crossed a line where describing what you want in plain language produces real, running software. People call it vibe coding. I call it the reason a 50-year-old security guy has apps in production.

What the AI handles — and what stays on your plate

Claude Code writes essentially all of my code. Syntax, frameworks, boilerplate — the things that used to take years to learn are the machine's job now.

What it can't supply: judgment, taste, and stubbornness. You decide what to build and, harder, what not to. You notice when the app technically works but feels wrong. You keep showing up on the evenings when the login flow still breaks. None of that got automated, and that part is the job.

The parts that still hurt

From my own builds:

• The unglamorous 80 percent. The demo took evenings; accounts, payments, and polish took the weeks after. I wrote up the real timelines in how long it takes to build an app with AI.
• App review. Getting PairHabit through the App Store taught me more about Apple's rules than I ever wanted to know.
• Understanding enough. You don't need to write code, but you do need to slowly learn what the pieces are — or you'll ask for the wrong things and believe the wrong answers.

None of this is a reason not to start. It's what the road looks like.

Who should skip it

If you want passive income without ever looking at an error message, skip this. The tools are remarkable; they are not magic. What they removed is the training. The work is still yours.

How I'd start this week

Pick one small annoyance from your own life. Not a startup idea — an annoyance. Describe it to an AI coding tool the way you'd brief a colleague. Ship the ugly first version to exactly one person. Everything I've learned came from that loop, repeated in the margins of a full-time job and two kids.