Public: anyone can read this; the crew can change it.
Migrated from github.com/Trevato/SO-ARM100
Mobile shell: video pinned on top, one status strip, bottom tabs, a snap-point drive sheet - and exactly ONE stop button #82
On a phone the camera now sits on top (16:9, full width) with the 3D model directly below it, both always on screen, and the model is the main control. Touch a part of the arm and drag to move that joint; it streams live through the existing 30 Hz latest-wins path. The joysticks and the one-joint lever are gone.
stopped parked by the crew deploy 7c1b0a4
On a phone the camera now sits on top (16:9, full width) with the 3D model directly below it, both always on screen, and the model is the main control. Touch a part of the arm and drag to move that joint; it streams live through the existing 30 Hz latest-wins path. The joysticks and the one-joint lever are gone. No screenshots in this pull: this sandbox blocks the sockets Chrome needs, so I couldn't open the page in a browser. Nothing in this pull has been looked at on a screen yet.
Layout
- Portrait: camera, then the status strip, then the model filling the space down to the tray of the open tab and the tab bar. Tabs are Drive · Queue · Chat · Admin · Machine.
- Tapping the open tab again folds its tray away and the model gets the room. - The tray has a fixed height, so filling it doesn't shift anything.
- Landscape (height ≤ 500 px): the strip with STOP runs across the top, and camera and model sit side by side under it.
- The sheet is a third column only while shown. It's put away when your turn starts, and Show brings it back.
- Wide screens: camera, model and sheet as three columns; only there can the 3D button put the model away.
- On a phone, a camera the owner listed now shows next to the model even when the arm is simulated. Before, only one view fit, so it stayed hidden.
Driving
- One finger on a part turns its joint; one finger on empty space does nothing. Two fingers turn the view and pinch zooms; neither sends anything to the arm.
- The model shows where you asked the arm to be. A faint blue ghost shows where the real arm is, but only while the two differ, so you can see the lag.
- The Drive tray lists every joint at once, one row each (name · slider · value), with the target and actual marks. A vertical swipe on a row scrolls the tray.
- Removed, with their code and tests: the thumb sticks, the gripper joystick (
src/ui/reach.js), and the chips + lever + nudges, i.e. all ofsrc/ui/drive.js.
Notes and STOP
- Nothing is drawn over the camera or the model. Zone warnings, jams, reconnecting, link problems, the speed cap, the owner's announcement and the page's own messages are counted in one "N notes" pill in the strip. It turns red when one is serious; a tap opens them all in a sheet. This lives in the new
src/ui/notes.js, which has unit tests. - A stop is a full-width row under the strip, with the two-tap Resume driving.
- There is exactly one STOP: red, 56 px tall, in the strip in every layout, and it fires on press.
Tests
server.test.tsassertions about the lever, sticks, chips anddrive.jsnow assert those are gone. Those tests weren't wrong; the UI they checked was removed on purpose.relay.test.tsusesintent.jsinstead of the deletedreach.jsas its example module.- New
src/phone-layout.test.tsopens the page in headless Chrome, with no new dependency, at 390x844, 412x915, 844x390 and 915x412, in light and dark. It checks:
- exactly one visible [data-stop], at least 56 px and inside the viewport;
- camera and model both on screen without overlapping, with the camera full-width 16:9 above the model in portrait;
- no notice over either view and no control under the forge pill, including with the sheet shown on its side;
- the tray folds and comes back;
- the stop row is full width and leaves one STOP.
- That suite was skipped here, with its reason printed; the rest of
bun testandtscpass. The forge's check will run it if its machine can start Chrome; if not, it skips the same way. WithPHONE_SHOTS=<dir>it saves a screenshot of every state, which are the ones to attach.
Not done: I didn't test one-handed with the camera as a draggable picture-in-picture over the model, so this pull has only the stacked layout. Haptics, the wake lock and the lag readout are unchanged.
To try it: open the preview on a phone. It runs locally with no sign-in, so the Drive tab opens straight away. Drag the gripper or elbow on the model, tap Drive again to fold the tray, press Stop, then turn the phone on its side.
🤖 Generated with Claude Code
Parked by the crew: the preview's deploy failed in the place it ran, not in the change, and it could not be run again
On a phone the camera now sits on top (16:9, full width) with the 3D model directly below it, both always on screen, and the model is the main control. Touch a part of the arm and drag to move that joint; it streams live through the existing 30 Hz latest-wins path. The joysticks and the one-joint lever are gone. No screenshots in this pull: this sandbox blocks the sockets Chrome needs, so I couldn't open the page in a browser. Nothing in this pull has been looked at on a screen yet.
Layout
- Tapping the open tab again folds its tray away and the model gets the room. - The tray has a fixed height, so filling it doesn't shift anything.
- The sheet is a third column only while shown. It's put away when your turn starts, and Show brings it back.
Driving
src/ui/reach.js), and the chips + lever + nudges, i.e. all ofsrc/ui/drive.js.Notes and STOP
src/ui/notes.js, which has unit tests.Tests
server.test.tsassertions about the lever, sticks, chips anddrive.jsnow assert those are gone. Those tests weren't wrong; the UI they checked was removed on purpose.relay.test.tsusesintent.jsinstead of the deletedreach.jsas its example module.src/phone-layout.test.tsopens the page in headless Chrome, with no new dependency, at 390x844, 412x915, 844x390 and 915x412, in light and dark. It checks:- exactly one visible
[data-stop], at least 56 px and inside the viewport; - camera and model both on screen without overlapping, with the camera full-width 16:9 above the model in portrait; - no notice over either view and no control under the forge pill, including with the sheet shown on its side; - the tray folds and comes back; - the stop row is full width and leaves one STOP.bun testandtscpass. The forge's check will run it if its machine can start Chrome; if not, it skips the same way. WithPHONE_SHOTS=<dir>it saves a screenshot of every state, which are the ones to attach.Not done: I didn't test one-handed with the camera as a draggable picture-in-picture over the model, so this pull has only the stacked layout. Haptics, the wake lock and the lag readout are unchanged.
To try it: open the preview on a phone. It runs locally with no sign-in, so the Drive tab opens straight away. Drag the gripper or elbow on the model, tap Drive again to fold the tray, press Stop, then turn the phone on its side.
🤖 Generated with Claude Code
Closes #49