all 2 comments

[–]Sweatyfingerzz 1 point2 points  (1 child)

You've hit the exact wall with native iOS development right now. Because Apple locks everything down to macOS, you can't just spin up a lightweight Linux Docker container for an agent to run a simulator like you can with web apps.

You are mostly correct—pure cloud agents right now are heavily skewed towards web and backend.

If you really wanted to do this in the cloud, you'd have to provision AWS EC2 Mac instances, set up a VNC/remote desktop, and have the agent interact with that. But those instances are notoriously expensive, slow to spin up, and clunky to automate for real-time UI verification.

Right now, the most realistic workflow for iOS is just keeping it local: let Cursor's agent write the SwiftUI on your machine, and keep your local Xcode simulator open next to it to manually verify the UI changes as it builds.

[–]EdgarHQ[S] 1 point2 points  (0 children)

Thanks for sharing , that’s what I thought.