You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,8 +35,8 @@ view inside the editor.
35
35
36
36
## Features
37
37
38
-
- Local iOS Simulator and Android emulator video over browser-native WebRTC H.264 with H.264 WebSocket fallback
39
-
- Android emulator frames are sourced from emulator gRPCand encoded through macOS VideoToolbox
38
+
- Local iOS Simulator video over browser-native WebRTC H.264 with H.264 WebSocket fallback
39
+
- Android emulator frames are sourced from emulator gRPC; loopback browsers use raw RGBA over WebRTC, and non-loopback browsers use VideoToolbox-encoded H.264
40
40
- Full simulator control & inspection using private iOS accessibility APIs and Android UIAutomator - available using `simdeck` CLI
41
41
- Real-time screen `describe` command using accessibility view tree - available in token-efficient format for agents
42
42
- CoreSimulator chrome asset rendering for device bezels
|`features/accessibility/`| Accessibility tree pane and source switcher. |
50
+
|`features/toolbar/`| Top toolbar (rotate, home, app switcher, dark mode toggle, refresh). |
51
51
52
52
## Bootstrap flow
53
53
@@ -56,7 +56,7 @@ client/
56
56
3.`AppShell` calls `GET /api/health` to learn the active encoder mode.
57
57
4. The simulator sidebar fetches `GET /api/simulators` and renders the list.
58
58
5. Selecting a device posts an SDP offer to `/api/simulators/<udid>/webrtc/offer`.
59
-
6. The browser renders the H.264 video track through native WebRTC playback. Android emulator frames are sourced from emulator gRPC on the server and encoded through VideoToolbox before WebRTC delivery.
59
+
6. The browser renders the WebRTC stream. iOS uses an H.264 media track; Android loopback clients use a raw RGBA data channel, while non-loopback Android clients use VideoToolbox-encoded H.264.
60
60
7. Touch and key events round-trip through `POST /api/simulators/<udid>/touch` and `/key`.
0 commit comments