Several challenges were noted during the implementation of WebXR in Unity applications. Browser compatibility posed significant challenges due to inconsistent WebXR support across various browsers and devices. This inconsistency affects the user experience as not all browsers can uniformly support WebXR. Performance issues emerged particularly when rendering complex scenes, which often results in bottlenecks causing inefficiencies. Debugging was complicated by the need to interface between C# and JavaScript, increasing the complexity of identifying and solving issues. Additionally, there were limitations in AR support because of constraints within Unity's WebGL build, impacting the effectiveness of AR functionalities .

SimpleWebXR's components play critical roles in facilitating the development of VR/AR experiences within Unity applications. SimpleWebXR.cs acts as the main C# script that interfaces directly with WebXR functionalities, handling events and processes necessary for running VR/AR environments. SimpleWebXR.jslib serves as a JavaScript library that forms the bridge between Unity's environment and the capabilities provided by the WebXR API. This connectivity allows for the execution of VR/AR processes in web browsers by translating Unity's complex environments and interactions into a format that browsers can execute, ultimately supporting the deployment of immersive experiences without dedicated native applications .

Within Unity's architecture for browser-based VR/AR experiences, WebGL is crucial as it allows for the rendering of interactive 3D graphics, enabling Unity scenes to be visualized in web browsers. Unity exports projects as WebGL builds which are essential for web compatibility, thereby facilitating the transition from development to live execution in browsers. The JavaScript Bridge, particularly embodied by SimpleWebXR.jslib, connects Unity's C# code with the WebXR Device API, enabling seamless communication and execution of WebXR commands. This bridge is pivotal in supporting runtime VR/AR functionalities, as it allows the integration of Unity's complex logic with the browser's execution environment to render immersive experiences .

The main technologies used for integrating Unity 3D applications with the WebXR API are the Unity Engine, WebXR Device API, WebGL, C# scripting, and a JavaScript Bridge. The Unity Engine serves as the primary development platform for creating the 3D environments. The WebXR Device API allows for VR/AR experiences directly in web browsers. WebGL renders interactive 3D graphics essential for displaying these environments in browsers. C# scripting addresses the application logic within Unity, and the JavaScript Bridge connects Unity's C# code to the WebXR API, enabling seamless execution of VR/AR experiences in browsers .

The demo scenes showcased successful integration and operational capabilities of Unity applications running VR/AR experiences directly in browsers. These interactive demos highlighted functionalities such as hand tracking, controller input processing, and spatial interactions. Users were able to access immersive experiences without needing native applications, demonstrating the capability and accessibility provided by the integration. This setup also facilitated testing across different scenes, like immersive VR in Oculus Browser and AR pass-through on Hololens, albeit with some limitations .

The Unity's XR Input System plays a crucial role in mapping Unity's input handling to the WebXR controller schema, which is essential for managing user interactions within VR/AR environments. It provides a framework for integrating diverse input sources, such as various VR controllers, to ensure they work smoothly in browser-based VR/AR applications. By translating input commands to be consistent with the WebXR framework, it enhances user interactions by allowing natural and responsive action within the immersive experiences. This is crucial for maintaining an engaging and intuitive user interface, which is fundamental for user immersion and experience satisfaction in VR/AR applications .

To address challenges and expand the future scope of WebXR-supported Unity applications, the project plans to enhance AR features by expanding the capabilities of Unity's WebGL builds, which are currently limited in supporting full AR functionalities. Performance optimization is another focus area, aiming to improve the rendering efficiency for complex scenes, which should alleviate the existing performance bottlenecks. The project also seeks to increase compatibility across a wider range of devices and browsers to overcome the current inconsistencies in WebXR support. Additionally, encouraging community contributions through open-source development is envisaged to foster innovation and further development of WebXR capabilities within Unity projects .

To overcome the inconsistencies in WebXR compatibility across different platforms, the project has planned to broaden device and browser support. This involves ensuring that the WebXR capabilities are consistent across various environments, emphasizing more robust compatibility checks and possibly developing additional layers of abstraction or emulation. Additionally, there may be efforts to engage with browser developers to address specific shortcomings in current WebXR implementations. By establishing a more versatile compatibility framework, it would enable a wider audience to access WebXR experiences reliably from different devices and platforms, improving overall user reach and application effectiveness .

The limitations in AR functionalities observed in Unity's WebGL builds primarily affect the deployment and scalability of AR experiences. These constraints may stem from the WebGL build's inability to fully utilize AR device features or efficiently render complex AR scenes directly in browsers. As a result, the richness and interactivity of AR experiences can be compromised, affecting user engagement and satisfaction. Such limitations can also elevate the technical complexity required in the development phase, requiring workarounds or additional development efforts to realize the intended AR functionalities within browser environments .

The key difference in performance between the ViT and ResNet models was in their overall accuracy and consistency across categories. ViT achieved a higher overall accuracy of 90.07% compared to ResNet's 89.38%. Additionally, ViT had a better macro-averaged F1 Score of 90.0% compared to ResNet's 89.21%. ViT's consistency across all classes, especially in difficult categories such as Viral Pneumonia, suggests it may be more reliable under variable conditions. However, ResNet performed very strongly in detecting Tuberculosis and Corona Virus Disease, indicating its robustness in specific applications. These performance differences influence model selection based on specific detection needs, with ViT potentially offering broader and more consistent applicability .