Documentation
This is the documentation page for TLabWebView. The contents will be updated as needed.

What is TLabWebView?
TLabWebView is a Plug-in to use Android's web browser component (WebView / GeckoView) as uGUI (Texture2D). Works on mobile and VR devices (e.g. Oculus Quest). This plugin makes it possible to implement a 3D web browser (3D WebView) within Unity.
The goal of the development
Independent of developer tools
Meta XR SDK, XR Interaction Toolkit, MRTK, VRIF ...., there are some developer tool for Unity but they are usually based on PointerEvent for uGUI interaction. TLabWebView's touch panel interaction is also developed based on PointerEvent for high compatibility and easy integration with any development tool.
Supports both OpenGL and Vulkan
This plugin supports both Vulkan and OpenGLES, but if you are building an application that uses a Vulkan graphics API, the Android device must support OpenGLES (3.1+) as well as Vulkan.
Supports both WebView and GeckoView for the browser engine
This plugin supports WebView and GeckoView for the browser engine, but currently the GeckoView feature is only developed with version 125.0.20240425211020 and needs API level 33+ for build. WebView and GeckoView are mostly same, but WebView doesn't need to include browser engine library (like gekoview-*.aar) in the app, and this is benefit for reduce app size. Also, WebView could send message from javascript to Unity CSharp easily, it has benefit for interaction with browser and Unity CSharp. In contrast, GeckoView needs to include browser engine library in the app, but more customizability than WebView for popup UI event. Currently, uGUI based html5 popup (select tag, datatime-local, etc ...) are supported only in GeckoView.
How to get it
The source code is available on GitHub. Please click on the links below to obtain samples that suit your purpose.
Donation
TLabWebView is open source and therefore free to use, but donations motivate development.
Note
Scripting API page removed to maintain integrity between source and document. Currently groping for a way to automatically reflect the original source's xml summary on the gitbook's scripting API page.
Discussion
Last updated
