The front-facing camera API enables WebXR-powered experiences to express their preference to use a front-facing (or "selfie") camera when creating immersive sessions. Some XR device form factors, most notably smartphones, have multiple cameras that can be used to power an immersive (generally AR) experience. The native AR frameworks already allow developers to configure the AR session by selecting the camera to be used - front-facing camera API exposes this configuration knob through WebXR.
Some XR device form factors, most notably smartphones, have multiple cameras that can be used to power an immersive (generally AR) experience. The native AR frameworks allow developers to configure the AR session by selecting the camera to be used; however, this configuration knob is currently unavailable in WebXR. The front-facing camera API changes that by enabling sites to express their preference to use a front-facing camera when creating immersive sessions. There are currently no (easy) possible workarounds to this feature gap - the sites would have to write custom AR frameworks, possibly on top of existing `getUserMedia()` and `DeviceOrientation` APIs.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No milestones specified