I Did Not Know How to Code. I Built Two Apps Anyway.

One week. Two apps. Zero coding background. Here is exactly how it happened.

I am not a developer. I am a project manager, a leadership coach, and someone who got tired of paying $15 a month for a breathing app that did one thing. So I asked a simple question: what if I just built something better?

That question turned into QuietPulse and RACEprompt — two apps now live on the App Store, built entirely with AI tools and a lot of iteration.

The QuietPulse Story: Solving My Own Problem

I was using a popular breathing app on my Apple Watch. Fifteen dollars a month. I used exactly one feature: haptic-guided breathing. That was it.

So I did what any frustrated user would do in 2026 — I had AI research every complaint people had about the top breathing apps on the market. What were people paying for that they did not need? What was actually missing?

The answer was simple: people wanted haptic breathing on their wrist without the subscription bloat. That became QuietPulse — haptic breathing for Apple Watch. No subscription. No account required. Just breathe.

Download QuietPulse on the App Store

The RACEprompt Story: Turning a PDF Into an App

I had been sharing a prompt-building framework called RACE (Role, Action, Context, Expectation) as a static PDF. It worked well enough, but I kept thinking: what if it did not just list the components — what if it actually built the prompts for you?

So I took the framework and turned it into an interactive app. You pick a scenario, fill in the blanks, and RACEprompt generates a structured AI prompt you can copy and use immediately. No prompt engineering knowledge required.

Fifteen-plus rounds of testing with real users in 48 hours. That is not a typo. AI let me iterate faster than any traditional development cycle could.

Download RACEprompt on the App Store

The Tools and Process Behind Both Apps

Here is what the actual process looked like:

• AI for research: I used AI to analyze app store reviews, identify gaps in existing products, and validate that real people wanted what I was building.
• AI for development: Claude, ChatGPT, and other AI tools helped me write Swift code, debug issues, and build functional prototypes — all without me knowing Swift beforehand.
• AI for iteration: Every round of user feedback went back through AI for analysis. What patterns were emerging? What needed to change? AI processed feedback faster than I could read it.
• AI for deployment: From App Store descriptions to metadata optimization, AI assisted with every step of getting both apps published.

The total timeline from idea to App Store for both apps combined: one week.

Why This Matters: The Rise of the Citizen Developer

MIT recently named this approach "vibe coding" — their number one breakthrough technology of 2026. The idea is straightforward: you do not need a computer science degree to build software anymore. You need a clear problem, the willingness to iterate, and AI tools that can translate your intent into working code.

The numbers back this up. Gartner predicts that by 2026, citizen developers will outnumber professional developers 4 to 1. That is not a threat to developers — it is an expansion of who gets to build solutions.

I am proof of that expansion. A project manager who builds apps. A leadership coach who ships software. The barriers are not gone, but they are dramatically lower than they were even a year ago.

What I Learned Along the Way

Building two apps in a week taught me a few things worth sharing:

• Start with frustration. Both apps came from real problems I was experiencing. If you are annoyed by something, other people probably are too.
• Iterate relentlessly. The first version of everything was rough. AI made it possible to go through 15-20 revision cycles in the time it would normally take to do two or three.
• Ship imperfect. Neither app was perfect on launch day. They were good enough to be useful, and that is what matters.
• Listen to users immediately. Real user feedback within the first 48 hours shaped both apps more than any amount of planning could have.

What Comes Next

Subscribers asked for Android versions. So I had AI convert the iOS apps. Done. That is a story for another post (coming next week), but the short version is: AI does not just help you build — it helps you expand to new platforms faster than you thought possible.

If you want to follow along as I document every step of this journey — the wins, the failures, the tools, and the process — join the AI Wins newsletter. I send one email per week breaking down exactly how I am using AI to build real things.

And if you want to see this process live, I am hosting a subscriber-only Q&A session on Friday, March 6 at 10:00 AM Mountain Time. No slides. No pitch. Just a walkthrough of how I built both apps, the tools I used, and answers to your questions.

You do not need to be a developer. You just need to know what frustrates you and be willing to build the fix.