iPhone app quickstart
- Source
- danromero.org
- Date

Context
Dan Romero's iPhone app quickstart is a single prompt meant to be pasted into a coding on a Mac, which then walks the user from an empty folder to a SwiftUI app running on their own iPhone. Romero wrote on X that he has been building personal iOS apps and asked Claude to help write the prompt from what it had struggled with and then learned along the way. So many of its rules read as fixes for places where Apple's toolchain tripped up an agent, written as instructions for the next one. The page says it was tested with Xcode 27.2 and iOS 27 and was updated on November 19, 2026.
Many of its rules head off failures that would otherwise show up later. The prompt tells the agent to set the app's minimum iOS version to the phone's version or lower, because Xcode otherwise defaults to the version of its own SDK and the build then cannot find an older phone. It tells the agent to set Swift 6.0 first, because new projects start at Swift 5.0 and changing it later is far harder. Every permission, such as camera access, needs a description string, or the app crashes when it asks. Before building anything, the agent is to establish whether the user has a free or paid Apple developer account: a free one cannot use push notifications, iCloud or Sign in with Apple, its builds stop opening after 7 days, and only 3 such apps fit on a phone at once, while the paid program costs $99 a year.
The other half of the prompt is about how the agent checks its own work. It builds and screenshots the app in Apple's simulator before showing the user, then installs on the real phone with a supplied script that builds, installs over the previous copy so saved data survives, launches the app and confirms it is still running five seconds later. The prompt explains why that last check exists: tests can pass in the simulator on an app that cannot launch on a phone. It also tells the agent never to uninstall the app to fix a problem, since that erases its data, to save data as versioned JSON files with a backup copy rather than in Apple's database frameworks, and to ask before uploading anything to Apple's TestFlight beta service. Because the simulator's command-line tools cannot tap, the prompt points to computer use or a simulator-control server for exploring the app; Claude Code Desktop's simulator pane is one tool that lets Claude tap through an app itself.
The prompt is one person's tested recipe, not a measured method. The page reports no success rate, and some instructions depend on the exact Xcode version, such as editing project.xcproj, which the prompt describes as Xcode 27.2's readable project file, while on Xcode 27.1 or earlier the agent is told to change build settings in Xcode's own settings tab instead. Romero's post invites feedback on it.
- Dan Romero's prompt says a free Apple developer team cannot use push notifications, iCloud or Sign in with Apple, its builds stop opening after 7 days, and only 3 free-team apps fit on one phone; the paid team costs $99 a year.
- It has the agent set SWIFT_VERSION to 6.0 in every target first, since new projects start at 5.0 and changing it later is far harder, and set the deployment target to the phone's iOS or lower, because Xcode defaults to its own SDK.
- Its phone.sh script builds, installs over the existing copy so the app keeps its data, launches, and checks after 5 seconds that the process is still running, because simulator tests can pass on an app that cannot launch on a phone.
- It recommends saving Codable structs as versioned JSON in Application Support with atomic writes, which it calls easier to inspect, migrate and recover than SwiftData or Core Data, and keeping the last good file instead of overwriting unreadable data.
- It flags two silent failures: a missing usage string such as NSCameraUsageDescription crashes the app when it asks for permission, and an app using only HTTPS, hashing and the Keychain must set ITSAppUsesNonExemptEncryption to NO or TestFlight testers cannot install it.
- AI agent — An AI system that doesn't just answer once but works toward a goal in a loop — taking actions, reading the results, and deciding what to do next.
Checking sign-in…
Loading comments…

