@limrun/ui 0.9.0-rc.10 → 0.9.0-rc.12

package/README.md

@@ -4,15 +4,6 @@
 
 See [examples](../../examples/) to see how it can be used.
 
-## Real Device Installation
-
-`@limrun/ui` also includes a browser-based iPhone installation flow:
-
-- `@limrun/ui/device-install/react` exports the headless `useDeviceInstall` hook for clients that want to render their own UI.
-- `@limrun/ui/device-install` exports the guided `DeviceInstallDialog` UI, which walks users through a signed device build, USB access, browser pairing, and installation.
-
-WebUSB requires a Chromium browser and a secure context. Pair records and signing assets, including the `.p12` password, are stored in the browser's IndexedDB.
-
 ### Releasing
 
 This package is not part of generated SDK, hence you need to publish it manually in GitHub Actions.

package/dist/components/remote-control.d.ts

@@ -93,6 +93,34 @@ interface RemoteControlProps {
      * @default 2000
      */
     axMaxBackoffMs?: number;
+    /**
+     * Optional outbound camera input.
+     *
+     * When provided, every video track on this `MediaStream` is forwarded
+     * up the same `RTCPeerConnection` that already carries the device
+     * screen downstream. On iOS instances, the limulator-side injector
+     * splices those frames into apps that use AVFoundation, so the user's
+     * browser camera becomes the iOS camera (`AVCaptureDevice.default(for:
+     * .video)`).
+     *
+     * Today this is only honored by iOS instances launched with the
+     * camera runtime; Android instances ignore it.
+     *
+     * Lifecycle expectations:
+     * - Pass `null`/`undefined` to skip outbound camera (default).
+     * - Pass a `MediaStream` obtained from
+     *   `navigator.mediaDevices.getUserMedia({ video: true })` (or any
+     *   other source — screen capture, virtual camera, etc.).
+     * - Changing the `MediaStream.id` triggers a connection restart so
+     *   the new track is included in the SDP offer. The reference itself
+     *   is allowed to be unstable across renders — we key the reconnect
+     *   on `id`, not object identity, so memoization isn't required.
+     * - Stopping the tracks (e.g. `track.stop()`) on the parent side is
+     *   sufficient to cut the outbound feed without restarting; the peer
+     *   connection just stops getting frames on that track. To fully
+     *   detach the track from the SDP, swap the prop to `null`.
+     */
+    cameraStream?: MediaStream | null;
 }
 interface ScreenshotData {
     dataUri: string;