I kept running into friction when working with iOS simulators across different setups (remote machines, CI, multiple devices). Most tools let you run things remotely, but not really interact with them in a natural way.
One concrete case was wanting to manually interact with an app running on a remote machine, without going through the whole TestFlight flow just to test something quickly.
This also fits nicely with CLI-driven workflows (like Claude Code or Codex), where you might trigger things programmatically but still want to step in and interact when needed.
So the focus with SimCast is making the simulator feel “present” even when it’s not local — being able to see it, interact with it, and plug it into those workflows.
florinmatinca•1h ago
I kept running into friction when working with iOS simulators across different setups (remote machines, CI, multiple devices). Most tools let you run things remotely, but not really interact with them in a natural way.
One concrete case was wanting to manually interact with an app running on a remote machine, without going through the whole TestFlight flow just to test something quickly.
This also fits nicely with CLI-driven workflows (like Claude Code or Codex), where you might trigger things programmatically but still want to step in and interact when needed.
So the focus with SimCast is making the simulator feel “present” even when it’s not local — being able to see it, interact with it, and plug it into those workflows.
Curious if others are solving this differently.