Vibe Coding with Claude Code: How I Build iOS Apps Faster with AI

If you told me two years ago that I’d be pair-programming with an AI to build iOS apps, I would have laughed. Today, Claude Code is one of the most important tools in my indie dev workflow — right alongside Xcode and a strong cup of coffee.

This post walks through how I actually use Claude Code day-to-day to build and ship apps at ZenoLab. Not the hype, not the theory — just practical workflows that save me hours every week.

What Is Vibe Coding?

Before we get into the tools, let me explain the philosophy behind how I work.

Vibe Coding is about trusting your intuition and moving fast. Instead of spending weeks planning architecture documents, I prototype quickly, ship early, and iterate based on real user feedback. The goal is to stay in a creative flow state — and AI is the perfect companion for that.

When I’m in the zone and I hit a friction point (how do I implement this animation? what’s the right CoreData migration pattern?), I don’t want to break flow by spending 30 minutes reading Stack Overflow. I ask Claude Code, get an answer in seconds, and keep building.

My Workflow: From Idea to App Store

Here’s how a typical app goes from idea to shipped product at ZenoLab.

1. Brainstorming & Research

I start by describing the app concept to Claude Code in plain English. For example, when building SnoozeLog (my AI-powered snore recorder), I started with:

“I want to build an iOS app that records audio while the user sleeps, detects snoring patterns using on-device ML, and shows a morning report with sleep quality score.”

Claude Code helped me break this down into concrete technical decisions: which audio framework to use (AVAudioEngine), how to run ML inference without draining the battery, and what the data model should look like.

2. Scaffolding with Swift & SwiftUI

Once I have a plan, I use Claude Code to generate the initial project structure. It’s particularly great for:

SwiftUI views — describing a UI and getting a working component back
Data models — CoreData entities, Codable structs, and relationships
Networking layers — API clients with proper error handling

I don’t blindly copy-paste. I treat Claude Code’s output as a very good first draft that I review, tweak, and integrate. Think of it as having a senior developer who writes code fast but still needs a code review.

3. The Hard Parts: Debugging & Edge Cases

This is where Claude Code really shines for solo developers. When you’re the only person on the team, there’s nobody to rubber-duck with. Claude Code fills that gap.

Some real examples from recent projects:

Sleep Tracker: Forest Aura — Had a tricky bug where background audio would stop after exactly 30 minutes on certain iPhone models. Claude Code identified it as an AVAudioSession category conflict and suggested the exact fix.
Liquid Focus — Needed to sync Pomodoro timer state across iPhone and Apple Watch. Claude Code walked me through WatchConnectivity step by step.
ProScan — PDF rendering was blurry on iPad Pro displays. Claude Code pointed out I was using the wrong scale factor for UIGraphicsImageRenderer.

4. Repetitive Tasks & Boilerplate

As an indie developer with 19 apps, there’s a lot of repetitive work: App Store descriptions, privacy policies, localization strings, unit test boilerplate. Claude Code handles all of this incredibly well.

I’ve automated several recurring tasks:

Generating App Store metadata (title, subtitle, keywords, description) optimized for ASO
Writing unit tests for ViewModels — I describe the behavior and get XCTest cases back
Creating localization files for multiple languages
Drafting release notes that actually sound human

5. Web Development with Astro

This very website (zenolab.app) was built with Astro, and Claude Code was my co-pilot throughout. From setting up Tailwind configurations to writing the SEO-optimized meta tags you see on every page, AI accelerated the entire web side of the business.

What Claude Code Is NOT Good At

Being honest about limitations is important. Here’s where I still do the work myself:

Visual design decisions — AI can write the code, but the creative direction (colors, spacing, animations) still comes from human taste
App Store screenshots — These need to be designed with marketing intuition, not generated
User empathy — Understanding why a user is frustrated requires human experience
Architecture for complex apps — For simple apps, AI architecture suggestions are fine. For anything with complex state management or real-time sync, I still design the architecture myself

Tips for Indie Devs Getting Started

If you’re a solo iOS developer thinking about adding AI to your workflow:

Start with the boring stuff — Let AI handle boilerplate, tests, and documentation first. This builds trust and saves immediate time.
Be specific in your prompts — “Write a SwiftUI view” is vague. “Write a SwiftUI view that shows a circular progress timer with a pulsing animation when active, using TimelineView for smooth updates” gets great results.
Keep your context focused — Claude Code works best when it understands your project. Feed it your actual code, not hypothetical examples.
Review everything — AI is a tool, not a replacement for understanding. If you can’t review the code it generates, you shouldn’t be shipping it.
Use it for learning — When Claude Code suggests a pattern I don’t recognize, I ask it to explain. It’s like having a patient tutor available 24/7.

The Numbers

Since integrating AI into my workflow:

Time from idea to App Store submission dropped from 3-4 weeks to 1-2 weeks
I’ve shipped 19 apps as a solo developer — something that would have been nearly impossible without AI assistance
Bug fix time decreased significantly — most issues get diagnosed in minutes, not hours
I spend more time on product decisions and less time on implementation friction

What’s Next

I’m continuing to push the boundaries of what a solo developer can build. AI tools like Claude Code are evolving fast, and I plan to write more about specific workflows — like how I use AI for App Store Optimization, automated testing strategies, and building cross-platform features.

If you want to follow along, check out the Build Journal for real-time updates, or browse the App Catalog to see everything I’ve shipped so far.

Have questions about using Claude Code for iOS development? Find me on X (Twitter) — I’m always happy to chat with fellow indie devs.