Merhaba Sevgili Floodlar.com Kullanıcısı, Web sitemizde geçirdiğiniz zaman ve bu büyüleyici flood evrenine katılımınız için teşekkür ederiz. Floodların geniş dünyasıyla dolu deneyiminizi daha fazla keşfetmek için, web sitemizi sınırsız olarak kullanabilmeniz adına giriş yapmanız gerekmektedir.

Oturum aç

Merhaba Floodlar.com Kullanıcısı, İlk üç sayfayı tamamladınız, tebrikler! Ancak, floodların devamını görmek ve daha fazla interaktif deneyim yaşamak için giriş yapmanız gerekiyor. Hesabınız yoksa, hızlıca oluşturabilirsiniz. Sınırsız floodlar ve etkileşimler sizleri bekliyor. Giriş yapmayı unutmayın!

Şifremi hatırlamıyorum

Şifreniz mi unuttunuz? Endişelenmeyin! Lütfen kayıtlı e-posta adresinizi giriniz. Size bir bağlantı göndereceğiz ve bu link üzerinden yeni bir şifre oluşturabileceksiniz.

Fil Necati Masonlar Locası Subreddit Adı Nedir? Cevap: ( N31 )

Üzgünüz, flood girme izniniz yok, Flood girmek için giriş yapmalısınız.

Lütfen bu Floodun neden bildirilmesi gerektiğini düşündüğünüzü kısaca açıklayın.

Lütfen bu cevabın neden bildirilmesi gerektiğini kısaca açıklayın.

Lütfen bu kullanıcının neden rapor edilmesi gerektiğini düşündüğünüzü kısaca açıklayın.

Mobil Uygulamada Açın

Güncel Floodlar En sonuncu Nesne

PWAs on Oculus Quest 2

PWAs on Oculus Quest 2

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 three browsers available for the Oculus Quest 2: Wolvic, a successor to 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)

As you can see, the current version 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.

Interacting with 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.

  1. On the Oculus device, browse to the desired site in Oculus Browser.
  2. Launch Google Chrome on your computer and navigate to chrome://inspect/#devices.
  3. Find the Oculus device in question, which will be followed by a set of Oculus Browser tabs currently open on the device.
  4. 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.

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 Bubblewrap CLI #

Bubblewrap is an open source set of libraries and a command line tool (CLI) for Node.js. Bubblewrap is developed by the Google Chrome team, to help developers generate, build, and sign an Android project that launches your PWA as a Trusted Web Activity (TWA).

Meta Quest Browser currently doesn’t fully support TWA, but starting from version 1.18.0, Bubblewrap supports packaging PWAs for Meta Quest devices.

It can generate universal APK files that open a TWA on regular Android devices and the Meta Quest Browser on Meta Quest devices.

Assuming you have Node.js installed, Bubblewrap CLI can be installed with the following command:

npm i -g @bubblewrap/cli

When running Bubblewrap for the first time, it will offer to automatically download and install the required external dependencies—Java Development Kit (JDK) and Android SDK Build Tools.

To generate a Meta Quest compatible Android project that wraps your PWA, run the init command with the --metaquest flag and follow the wizard:

bubblewrap init --manifest=" --metaquest

Once the project has been generated, build and sign it by running:

bubblewrap build

This will output a file called app-release-signed.apk. This file can be installed on the device or published to the Meta Quest Store, Google Play Store or any of the other Android app distribution platforms.

Packaging PWAs with Oculus Platform Utility #

Oculus Platform Utility is the official command line tool developed by Meta for publishing apps for Oculus Rift and Meta Quest devices.

It also allows to package PWAs for Meta Quest devices with the create-pwa command and publish them to the Meta Quest Store and App Lab.

Set the output file name via the -o parameter and the path to Android SDK via the --android-sdk parameter.

Point the tool at the live URL of the web app manifest via the --web-manifest-url parameter.

If you don’t have a manifest on your live PWA or wish to override the live manifest, you can still generate an APK for your PWA using a local manifest file and the --manifest-content-file parameter.

To leave the manifest as pure as possible, use the --package-name parameter with a value in reverse domain name notation (for example, 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.pwa

Packaging PWAs with PWABuilder #

Using PWABuilder is in the authors’ view the easiest and therefore recommended way to package PWAs for Meta Quest at the moment.

PWABuilder is an open source project developed by Microsoft, that allows developers to package and sign their PWAs for publishing to various stores, including Microsoft Store, Google Play Store, App Store, and Meta Quest Store.

Packaging PWAs with PWABuilder is as easy as entering the URL of a PWA, entering/editing the metadata for the app, and clicking the Generate button.

PWABuilder gives developers the choice of what tool under the hood to use for packaging PWAs for Meta Quest devices.

You can choose the Meta Quest option to use the Oculus Platform Utility.

İlgili Mesajlar

Yorum eklemek için giriş yapmalısınız.