iOS and Android simulator support #304

Open
opened 2026-10-29 14:59:46 -04:00 by cmoriarty · 1 comment
Owner

I know this is going to be challenging since the iOS simulator has to be run on apple products, but Braid needs to be able to simulate phone/touch interfaces for certain projects that require it. Currently it uses a browser for everything.

As always with Braid, I want complete transparency, so while the simulators are running, the user should be able to visually see exactly what is happening. Here is a screenshot of how Claude Code looks when using the simulator, and it is what I'm aiming for with Braid: image

The next consideration is how to offer the different agents the simulators. Briefs will likely need to updated for when apps require mobile support, and perhaps even new graph steps that ensure the simulator is used could exist, in addition to agents being asked to leverage it. Perhaps even research best practices for writing fast useful tests for simulators.

As a side quest - Braid already makes good use of playwright and browsers. For the times it is using the browser manually, it would be great if the user could see and watch that similar to these mobile simulators. I understand that ultimately the goal is to write fast scripted tests for these simulators, rather than having to drive them manually (much slower).

If seeing the live views of simulators and browsers for users to watch turns out to be difficult, it can be spun off into another ticket, and this one can focus on building the capabilities for agents to use.

I know this is going to be challenging since the iOS simulator has to be run on apple products, but Braid needs to be able to simulate phone/touch interfaces for certain projects that require it. Currently it uses a browser for everything. As always with Braid, I want complete transparency, so while the simulators are running, the user should be able to visually see exactly what is happening. Here is a screenshot of how Claude Code looks when using the simulator, and it is what I'm aiming for with Braid: ![image](/attachments/83ba2971-0a3d-4299-a8b5-70fe03f42312) The next consideration is how to offer the different agents the simulators. Briefs will likely need to updated for when apps require mobile support, and perhaps even new graph steps that ensure the simulator is used could exist, in addition to agents being asked to leverage it. Perhaps even research best practices for writing fast useful tests for simulators. As a side quest - Braid already makes good use of playwright and browsers. For the times it is using the browser manually, it would be great if the user could see and watch that similar to these mobile simulators. I understand that ultimately the goal is to write fast scripted tests for these simulators, rather than having to drive them manually (much slower). If seeing the live views of simulators and browsers for users to watch turns out to be difficult, it can be spun off into another ticket, and this one can focus on building the capabilities for agents to use.
image.png
1.2 MiB
Author
Owner

Groundwork filed as #432: the Visual check runs only for a file a browser renders and its brief is written for a browser, so a simulator today would mean no Visual check at all. #432 separates the neutral framework (criteria, rounds, look and carry lists, report, filmstrip, what is left to a person's eyes) from the web layer (how to open, drive, freeze and measure), so this issue can add a simulator layer beside the web one instead of forking the step.

Groundwork filed as #432: the Visual check runs only for a file a browser renders and its brief is written for a browser, so a simulator today would mean no Visual check at all. #432 separates the neutral framework (criteria, rounds, look and carry lists, report, filmstrip, what is left to a person's eyes) from the web layer (how to open, drive, freeze and measure), so this issue can add a simulator layer beside the web one instead of forking the step.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#304
No description provided.