r/iOSProgramming • u/samstars100 • 18h ago

Discussion iOS Development using OpenClaw.

I am using OpenClaw through telegram. I create web applications in VPS and web applications are pretty easy to vibe code and also test the output using public urls.

I want to do same for iOS Development. I want to connect to macOS using OpenClaw and develop iOS application completely through telegram. I can create a workflow where any changes will send build to TestFlight and I can test the application that way. But it will be time consuming, makeing build in testflight and test the app only updated through testflight. I want near realtime visualization of the compiled app like simulator but through web and http network. Do you guys have any idea how to achieve this?

0 Upvotes

9% Upvoted

9 comments sorted by

4

u/Gullible-Question129 17h ago

ask claude

0

u/samstars100 17h ago

I actually implemented it already using tailscale. I can now actually access the simulator from any devices in tailnet. I was just curious there is better way.

1

u/Kovsis 17h ago

You can try Android development on Google website and test your vibecoded app through their online emulators

Ios - nope, local and macOS only + get ready for 100$ yearly to test apps in TestFlight environment

Updated: typo

1

u/samstars100 17h ago

I already have dev account. I need to automate app development and I actually have developed POC . I hosted a python server which broadcasts simulator and other devices on tailnet can actually control the simulator through web app. Just curious to know if there are better mechanisms.

1

u/Background_Pie_5682 10h ago

TestFlight is way too slow as an inner loop for this. Since the Simulator needs macOS anyway, I'd let the agent on the Mac do build, install, launch and screenshot: xcodebuild to build for the simulator, `xcrun simctl install` and `launch` to run it, then `xcrun simctl io booted screenshot` (or `recordVideo`) to send the result back to Telegram after every change. If you want something closer to live, stream the Mac's screen with the Simulator open (VNC or screen sharing) and view it in the browser. Keep TestFlight for the occasional real-device check.

1

u/AdamHincu_ 10h ago

the tailscale simulator stream is a solid hack, but the slow part is still rebuild + reinstall on every change. if the app doesn't need to be pure swift, an expo dev build on your actual phone over the tailnet gets you the "agent edits, phone updates in a second" loop for js changes. if it has to be swiftui, i'd at least have the agent trigger xcodebuild + simctl install/launch after each edit so your stream refreshes on its own.

1

u/samstars100 6h ago

Yes that's what exactly I felt. Rebuild and reinstall is cumbersome with simulator stream. Expo would be best for hot reload in real device but my preference is swift and swiftui.