This content originally appeared on web.dev and was authored by Thomas Steiner
The Oculus Quest 2 #
The Oculus Quest 2 is a virtual reality (VR) headset created by Oculus, a division of Meta. It is the successor to the company's previous headset, the Oculus Quest. The device is capable of running as both a standalone headset with an internal, Android-based operating system, and with Oculus-compatible VR software running on a desktop computer when connected over USB or Wi-Fi. It uses the Qualcomm Snapdragon XR2 system on a chip with 6 GB of RAM. The Quest 2's display is a singular fast-switch LCD panel with 1,832 × 1,920 pixels per eye resolution that runs at a refresh rate of up to 120 Hz.
The Oculus Browser #
Currently there are two browsers available for the Oculus Quest 2, Firefox Reality and the built-in Oculus Browser. This article focuses on the latter. The Oculus website introduces the Oculus Browser as follows.
"Oculus Browser provides support for the latest web standards and other technologies to help you create VR experiences on the web. Today's 2D web sites work great in Oculus Browser because it's powered by the Chromium rendering engine. It's further optimized for Oculus headsets to get the best performance and to enable web developers take advantage of the full potential of VR with new APIs, like WebXR. Through WebXR, we're opening the doors to the next frontier of the web."
User agent #
The browser's user agent string at the time of writing is as follows.
Mozilla/5.0 (X11; Linux x86_64; Quest 2)
AppleWebKit/537.36 (KHTML, like Gecko)
OculusBrowser/18.1.0.2.46.337441587
SamsungBrowser/4.0
Chrome/95.0.4638.74
VR
Safari/537.36As you can see, the current version 18.1.0.2.46.337441587 of the Oculus Browser is based on Chrome
95.0.4638.74, that is only one version behind the current stable version of Chrome, which is
96.0.4664.110. If the user switches to mobile mode, VR changes to Mobile VR.
User interface #
The browser's user interface (shown above) has the following features (top row from left to right):
- Back button
- Reload button
- Site information
- URL bar
- Create bookmark button
- Resize button with narrow, medium, and wide options as well as a zoom feature
- Request mobile website button
- Menu button with the following options:
- Enter private mode
- Close all tabs
- Settings
- Bookmarks
- Downloads
- History
- Clear browsing data
The bottom row includes the following features:
- Close button
- Minimize button
- Three dots button with back, forward, and reload options
Refresh rate and device pixel ratio #
For Oculus Quest 2, Oculus Browser renders both 2D web page content and WebXR at a 90 Hz refresh rate. When watching fullscreen media, Oculus Browser optimizes the device refresh rate based on the frame rate of the video, for example, 24 fps. The Oculus Quest 2 has a device pixel ratio of 1.5 for crisp text.
PWAs in Oculus Browser and the Oculus Store #
On October 28, 2021, Jacob Rossi, Product Management Lead at Meta (Oculus), shared that PWAs were coming to Oculus Quest and Oculus Quest 2. In the following, I describe the PWA experience on Oculus and explain how to build, sideload, and test your PWA on the Oculus Quest 2.
State sharing #
Login state is shared between Oculus Browser and PWAs, allowing users to seamlessly switch between the two. Naturally, Facebook Login is supported out of the box. The Oculus Browser includes a password manager that allows users to store and share their passwords securely between the browser and installed app experiences.
PWA window sizes #
Browser windows and windows of installed PWAs can be freely resized by the user. The height can vary between 625 px and 1,200 px. The width can be set between 400 px and 2,000 px. The default dimensions are 1,000 × 625 px.
Controlling PWAs #
PWAs can be controlled with the Oculus left and right controllers, Bluetooth mice and keyboards, and via hand tracking. Scrolling works via the thumb sticks on the Oculus controllers, or by pinching the thumb and the index finger and moving in the desired direction. To select something, the user can point and pinch.
Permissions for PWAs #
Permissions in Oculus Browser work pretty much the same way as in Chrome. The state is shared between apps running in the browser and installed PWAs, so users can switch between the two experiences without having to grant the same permissions again.
Albeit many permissions are implemented, not all features are supported. For example, while requesting the geolocation permission succeeds, the device never actually gets a location. Similarly, the various hardware APIs like WebHID, Web Bluetooth, etc. all pass feature detection, but don't actually show a picker that would let the user pair the Oculus with a hardware device. I suppose feature detectability of APIs will be refined once the browser matures.
Debugging PWAs via Chrome DevTools #
After enabling Developer Mode, debugging PWAs on Oculus Quest 2 works exactly as described in Remote debug Android devices.
- On the Oculus device, browse to the desired site in Oculus Browser.
- Launch Google Chrome on your computer and navigate to
chrome://inspect/#devices. - Find the Oculus device in question, which will be followed by a set of Oculus Browser tabs currently open on the device.
- Click inspect on the desired Oculus Browser tab.
App discovery #
People can use the browser itself or the Oculus Store to discover PWAs. Just like with any other browser, installed PWAs also work in Oculus Browser as websites running in a tab. When a user visits a site, the Oculus Browser will help them discover the app if (and only if) it is available in the Oculus Store. For users that already have the app installed, Oculus Browser will help them easily switch to the app if they desire.
App submission #
Apart from submitting apps to the Oculus Store, developers can also submit their apps to App Lab, a way for developers to distribute apps directly to consumers safely and securely, via direct links or platforms like SideQuest, without requiring store approval and without sideloading. This allows them to get an app directly to end users, even if it is early in development, experimental, or aimed at a unique audience.
Exemplary PWAs on the Oculus Quest 2 #
PWAs by Meta #
Multiple Meta divisions have created PWAs for the Oculus Quest 2, for example Instagram and Facebook. These PWAs run in standalone app windows that don't have a URL bar and that can be freely resized.
PWAs by other developers #
At the time of this writing, there is a small but growing number of PWAs for the Oculus Quest 2 on the Oculus Store. Spike lets users experience all the essential work tools like email, chat, calls, notes, tasks, and to-dos from their inbox in a virtual environment hub right in the Spike app.
Another example is Smartsheet, a dynamic workspace that provides project management, automated workflows, and rapid building of new solutions.
More PWAs like Slack, Dropbox, or Canva are coming, as teased in a video featuring Jacob Rossi that was released in the context of Facebook's Connect conference in 2021.
Creating PWAs for Oculus #
Meta outlined the required steps in their documentation. In general, PWAs that are installable in Chrome should oftentimes work out of the box on Oculus.
Web App Manifest requirements #
There are some important differences compared to
Chrome's installability criteria and the
Web App Manifest spec. For example, Oculus only supports
left-to-right languages at the moment, whereas the Web App Manifest spec enforces no such
constraints. Another example is start_url, which Chrome strictly requires for an app to be
installable, but which on Oculus is optional. Oculus offers a
command line tool that lets
developers create PWAs for the Oculus Quest 2, which allows them to pass the missing (or
override the existing) parameters in the Web App Manifest.
Oculus has a number of optional proprietary Web App Manifest fields that can be used to customize the PWA experience.
Packaging PWAs with the command line tool #
To sideload PWAs onto the Oculus Quest 2, developers must use a
command line tool called
ovr-platform-util with the create-pwa command to generate the APK. Set the output file name via
the -o parameter. The Android SDK to use needs to be set via the --android-sdk parameter.
Assuming a manifest file called manifest.json in the current working directory, the
--manifest-content-file parameter helps the tool determine the relevant configuration fields from
the Web App Manifest. Alternatively, developers can point the tool at the live URL of a manifest via
the --web-manifest-url parameter. To leave the manifest as pure as possible, use the
--package-name parameter with a value in reverse domain name notation (e.g.,
com.company.app.pwa), rather than adding the proprietary ovr_package_name field to the manifest.
ovr-platform-util create-pwa -o output.apk --android-sdk ~/bin/android-10 --manifest-content-file manifest.json --package-name com.company.app.pwaInstalling PWAs with adb #
After creating the APK, developers can sideload the PWA with the adb command when the Oculus
Quest 2 device is connected via USB and when the connected computer is trusted. Sideloaded apps
appear in an Unknown Sources section in the app drawer.
adb install output.apkTesting multi-tab apps #
To test multi-tab apps, I created a little test PWA that demonstrates the various link features: namely opening a new in-PWA tab, staying on the current tab, opening a new browser window, and opening in a WebView staying on the current tab. Create a locally installable copy of this app by running the commands below on your machine.
ovr-platform-util create-pwa -o test.apk --android-skd ~/bin/android-10 --web-manifest-url https://tomayac.github.io/oculus-pwa-test/manifest.json --package-name com.example.pwa
adb install test.apkHere's a screencast of the test app.
An Oculus version of SVGcode #
To take the instructions for a spin, I created an Oculus version of my most recent PWA,
SVGcode. You can download the resulting APK file
output.apk
from my Google Drive. If you want to investigate the package further, I have a
decompiled version,
too. Find the build instructions in
package.json.
Using the app on Oculus works fine, including the ability to open and save files. The Oculus Browser doesn't support the File System Access API, but the fallback approach helps. The only thing that didn't function is pinch-zooming. My expectation was for it to work by pressing the trigger button on both controllers and then moving the controllers in opposed directions. Other than that, everything else was performant and responsive, as you can see in the embedded screencast.
Conclusions #
PWAs on Oculus Quest 2 are a lot of fun and very promising. The endless virtual canvas that lets users scale their screen to whatever fits the current task best has a lot of potential to change the way we work in the future. While typing in VR with hand tracking is still in its infancy and, at least for me, doesn't work very reliably yet, it works well enough for entering URLs or typing short texts.
What I like the most about PWAs on the Oculus Quest 2 is that they are just regular PWAs that can be used unchanged in a browser tab or through a thin APK wrapper without any platform-specific APIs. Targeting multiple platforms with the same code has never been easier. Here's to PWAs in VR and on the web. The future is bright!
Acknowledgements #
Oculus Quest 2 photo by Maximilian Prandstätter on Flickr. Oculus Store images of Instagram, Facebook, Oculus Browser, and Spike apps as well as app discoverability illustration and hand tracking animation courtesy of Meta. This post was reviewed by Joe Medley.
This content originally appeared on web.dev and was authored by Thomas Steiner
Thomas Steiner | Sciencx (2022-01-10T00:00:00+00:00) PWAs on Oculus Quest 2. Retrieved from https://www.scien.cx/2022/01/10/pwas-on-oculus-questnbsp2/
Please log in to upload a file.
There are no updates yet.
Click the Upload button above to add an update.