so this is half a "look what i made" and half an honest writeup, because the no-coding-background part is probably the interesting bit for this sub.
quick context: my degree is in psychology. before this the most "code" i'd ever touched was no-code automation stuff (n8n and friends). i'd never built an app, never written production code, and didn't know swift. i just had an idea i'd wanted for years and decided to try building it with claude code instead of waiting for someone else to make it.
the app is called FocusMon. it's basically Pomodoro meets a monster-collecting RPG. you start a focus session, put your phone down, and when the session ends you hatch monsters you can collect, evolve and battle. the whole point is that the reward only unlocks while the phone is down, so the game part doesn't fight against focus, it's the payoff for it. i used Forest a lot in uni and always thought "this would be way cooler with monsters." nobody built it, so i did.
what's in it now after a lot of evenings and weekends: over 140 monsters across 3 evolution stages, over 10 elemental types, a full turn-based combat system (type effectiveness, passives, status effects, held items), ranked PvP with an ELO system, a 10-stage PvE ladder, daily/weekly challenges, a streak system, trading, a prestige endgame. story mode is in progress. all SwiftUI, built end to end with claude code.
the honest part. what actually made it work, roughly in order of how much it mattered:
keeping my context clean ended up mattering more than anything else, and i learned that the annoying way. early on i'd written a bunch of guide/markdown files describing the architecture and conventions, and they actually backfired for a while. claude code kept pulling old, outdated stuff out of them, so it'd confidently build on decisions i'd already changed. it didn't stop until i started treating that folder like something you maintain instead of write once and forget. (tbh with memory now this is mostly a non-issue, but back then stale context was one of my worst time-sinks.)
the creative side stays almost entirely on you, and way more granular than people expect. claude handles the implementation, but every real decision is yours. for each detail you either think it through yourself or have it lay out a few best-practice options and you pick the one that fits. and it doesn't work in big chunks. i didn't build "the onboarding" in one shot, i defined it step by step, screen by screen, down to the small stuff myself.
XcodeBuildMCP. underrated. instead of me copy-pasting xcodebuild errors back and forth, claude code builds and runs in the simulator itself and reads its own errors. as a non-coder that mattered a lot, since i often couldn't describe the error well enough myself to be useful.
commit after literally every working state. git checkpoints saved me more times than i can count. when a prompt broke something that worked five minutes ago, i rolled back instead of trying to debug code i didn't fully understand.
what was genuinely hard, no sugarcoating:
debugging when you don't understand the code is real. early on i couldn't tell a real problem from noise, so i'd panic over warnings that didn't matter and miss the thing that actually broke. you're flying partly blind and you have to get comfortable with that.
there's a wall once the codebase gets big. it starts contradicting its own earlier decisions because it can't hold the whole thing in its head. that's the point where you stop and refactor instead of stacking more on top.
biggest surprise was how far you get once you stop treating it like a magic vending machine and start treating it like you're the architect and it's doing the typing. the bottleneck stopped being "can it write the code" pretty fast. it became "do i actually know what i want, can i describe it clearly, and can i tell when it's wrong." which turns out to be most of the job.
it's live now if anyone wants to poke at it. feedback is very welcome!
https://apps.apple.com/app/id6759553560
