Describe the what, let the agent navigate the how

I started building my first iPhone app this week.

I've bounced off this one for years. Not the ideas, I've had plenty of those, but the effort to actually build for iPhone. A lot of that friction lived in the developer ecosystem itself: getting set up on a free Apple account, navigating the UX of Xcode, the dozens of small "how do I even do this" steps that never had much to do with the app I actually wanted to make.

This time I worked with Claude. I could simply describe what I wanted, and the agent had no trouble navigating the how. The parts that used to stop me cold became something I could just ask about and move through.

The result: a working app, sideloaded onto my phone, in a couple of hours.

What strikes me is not that the agent wrote the code. It is that it dissolved the friction that had kept the door shut for so long. The barrier was never really the building, it was everything around it. And now that I have something running on my phone, I can dig into the Swift itself, a language that's new to me, and start to really understand how to build in it.