Skip to main content

Introduction

such as visual 3D space rendering is implemented based on modern browsers WebGL.In environments such as mobile terminals iOS / Android and micro-messenger applets are integrated in the form of a nested frontend page in WebView like 3D space rendering capability.At the same time, in order to take full advantage of the ends' capabilities, such as viewing the Open Platform as official encapsulation of the VRWebView SDK.

Support features

VRWebView mainly provides the following functions:

Terminal Capabilities

  • Basic functions:features like fullscreen, vibration, share, permission detect, access to albums etc. are not available at the browser.
  • Voice channel:is limited to WebRTC compatibility, terminal device can proxy WebRTC.

Performance experience

  • Preload capacity:Before turning on the VR page, you can preload some data, sticky resources and more.
  • First Rendering(partially supported):provides terminal rendering capability, pending seamless switching when front-end rendering is complete.
  • Proxy request(partially support):takes advantage of high client performance HTTP request capacity, and caches request results to avoid subsequent duplicate requests.

"bridge" protocol

@realsee/jsbridge-x is implemented VRWebView The frontend SDK for messaging and data exchange between the container and its embedded web page.

For more details, please move by way: "bridge" protocol - introduce.

Reminder

Due to the inconsistent implementation mechanism of WebView of each terminal (iOS WKWebView, Android WebView, WeChat applet web-view , etc.), although @realsee/jsbridge-x has tried to smooth out the differences between them, but due to the differences in platforms, please refer to the API corresponding to each version for details.