I’ve been using Cloud Agents with separate environments for my web apps, and they work really well there because the agent can run the app in a browser, test flows, and demo changes directly.
I’m wondering what the best practice is for native iOS development.
For iOS projects, a lot of us rely on Xcode-specific tooling, simulators, code signing, provisioning profiles, and environment config through .xcconfig files. That makes me question whether it’s worth setting up a full Cloud Agent environment for iOS apps in the same way as web apps.
At the moment, it feels like Cloud Agents are ideal for web stacks, but less clear for native mobile workflows unless there is strong support for:
-
Running iOS simulators remotely
-
Building with
xcodebuildreliably -
Handling signing / provisioning cleanly
-
Supporting multiple
.xcconfigenvironments -
Previewing UI changes similarly to browser demos
-
Integrating with Mac-based build infrastructure
I’d be interested to hear how others are using Cursor Cloud Agents for iOS projects.
Are people finding value in full remote environments for native iOS apps, or are most using agents mainly for code changes/refactors while keeping builds and simulator testing local?
Would also love to hear if Cursor has plans for stronger native mobile workflows in Cloud Agents.