Claude Code is not an editor. It is not an extension. It is a terminal agent that reads your code, writes code, runs commands, and handles git — all from your terminal. When I first tried it, I thought “why would I use a terminal tool when I have Cursor?” After one week, I understood. Claude Code does things that no IDE-based tool can match. Here is my honest review after months of daily use. ...
This is the capstone article. Everything from 14 projects comes together. We started this series with a CLI todo app that took 35 minutes. Then we built REST APIs, Chrome extensions, full-stack blogs, SaaS dashboards, and mobile apps. Each project taught us something about working with Claude Code. Now the question: can we take a real product idea — something that could make money — from concept to deployed, production-ready app in a single working day? ...
Mobile development is hard. Cross-platform mobile development is harder. Kotlin Multiplatform sits in the middle — shared business logic with native UI on each platform. The Gradle configuration alone can take hours. Can Claude handle it? This is the most technically challenging project in the entire series. KMP has expect/actual declarations, platform-specific dependency injection, multiplatform Gradle config, and two completely different UI frameworks (Jetpack Compose for Android, SwiftUI for iOS). ...
Every article so far has used one Claude Code session. One terminal, one conversation, one context. That works for small projects, but what about larger codebases where different parts can be built in parallel? Claude Code supports multiple agents working on the same project. You can have one agent building the backend, another building the frontend, and a third writing tests — all at the same time. This article tests whether multi-agent development actually works. Does it save time? What happens when agents step on each other’s code? How do you coordinate? ...
SaaS boilerplate kits sell for $200-$500 on marketplaces. They include authentication, Stripe subscriptions, admin panels, and billing portals. The same starter template, over and over. Let us build one with Claude in an afternoon. This is the most complex project in the series so far. Stripe’s webhook lifecycle, subscription state management, role-based access, and usage tracking all need to work together. A lot can go wrong. Total time: 5 hours 22 minutes. 7 prompts. Stripe webhooks took the most iteration. ...
Welcome to Part 3: Advanced Projects. We are done with quick builds and half-day apps. Now we tackle complex, multi-component systems. First up: a real-time chat application. WebSockets, authentication, rooms, typing indicators, online presence, message history. This is the kind of project that tests whether Claude can handle multiple moving parts that all need to work together in real time. Total time: 4 hours 38 minutes. 7 prompts. WebSocket auth was the hardest part. ...
After a full-stack blog, a weather dashboard, a desktop app, and a mobile app, we close Part 2 with something different: a backend microservice in Go. Go is interesting for vibe coding because the language is simple and opinionated. There is usually one way to do things. Claude should have an easier time generating idiomatic Go than, say, idiomatic Rust. Let us find out. Total time: 2 hours 14 minutes. 6 prompts. Go’s simplicity made this the fastest Part 2 project. ...
This is the hardest project in Part 2. Kotlin Multiplatform has a complex build system, platform-specific code patterns, and a Gradle configuration that can break in surprising ways. Can Claude handle it? I was skeptical going in. KMP projects have dozens of Gradle files, expect/actual declarations, and platform-specific dependencies that need to match exact versions. One wrong version number and nothing compiles. Total time: 4 hours 31 minutes. 6 prompts. Most of the time was fighting Gradle. ...
Building a desktop application is different from building a web app. You have to deal with the operating system: file dialogs, menu bars, keyboard shortcuts, window management. Electron makes this possible with web technologies, but the architecture — main process vs. renderer process — trips up many developers. Can Claude handle it? I gave it a full markdown editor spec and found out. Total time: 3 hours 47 minutes. 7 prompts. Electron’s IPC was the biggest time sink. ...
API integration is one of the things developers do most and enjoy least. Parsing JSON, handling errors, managing loading states, formatting data for charts. It is repetitive work. This is where Claude Code earns its keep. I gave it an API, a design goal, and a list of features. It handled the rest. Total time: 2 hours 38 minutes. 6 prompts. The charts took the longest. What We’re Building A weather dashboard with: ...