Phoenix is an AI coding agent built specifically for iOS development. It writes and edits code, runs builds and tools, diagnoses errors, and helps you take an iOS project from idea to working app.
Hi Product Hunt,
We built Phoenix because iOS development has a lot of repetitive work between writing code and actually getting an app running.
Phoenix is an AI coding agent built specifically for iOS development. It can work with your project, edit code, run builds and tools, diagnose errors, and help iterate towards a working app.
We wanted an agent that understands the realities of iOS development rather than treating an Xcode project like a generic codebase.
We'd love to hear from iOS developers:
What part of your iOS development workflow would you most want an AI agent to handle?
Try Phoenix and let us know what breaks, what works, and what you'd like to see next.
Report
Answering your question: the part I'd want handled is everything around the code, not the code. Generic agents write perfectly good Swift and then mangle the pbxproj adding the file, and you find out from a build failure that has nothing to do with what you asked for. The other one is telling a compile error apart from a signing or provisioning failure, because they look similar in the log and the fixes aren't related at all. Get those two right and the code writing matters a lot less than people assume.
@asadmalik901 Thank you for sharing this — really appreciate the perspective. The distinction between code issues and Xcode project, build, signing, or provisioning issues is an important one. It’s also a big part of what we’re focusing on with Phoenix.
Report
@sreejith_np Then I'd put the signing and provisioning side first, honestly. Code errors already have a dozen agents fighting over them, and the thing that actually eats my afternoon is working out which of six profiles is stale and why the archive won't upload. If Phoenix can read that error, name the wrong profile and fix it without me opening the developer portal, that's the demo I'd lead with.
Phoenix
Answering your question: the part I'd want handled is everything around the code, not the code. Generic agents write perfectly good Swift and then mangle the pbxproj adding the file, and you find out from a build failure that has nothing to do with what you asked for. The other one is telling a compile error apart from a signing or provisioning failure, because they look similar in the log and the fixes aren't related at all. Get those two right and the code writing matters a lot less than people assume.
Phoenix
@asadmalik901 Thank you for sharing this — really appreciate the perspective. The distinction between code issues and Xcode project, build, signing, or provisioning issues is an important one. It’s also a big part of what we’re focusing on with Phoenix.
@sreejith_np Then I'd put the signing and provisioning side first, honestly. Code errors already have a dozen agents fighting over them, and the thing that actually eats my afternoon is working out which of six profiles is stale and why the archive won't upload. If Phoenix can read that error, name the wrong profile and fix it without me opening the developer portal, that's the demo I'd lead with.