Agentic AI - Hands On Practices Agentic AI Hands-on practice for developing end to end AI agent, and understanding the internals. ☞ Github ☞ Learn More Python Hands On Practices Python Hands-on practice for developing end to end application, and understanding the language concepts. ☞ Github ☞ Learn More Gen AI Hands On Practices Google Colab Hands-on practice for developing Gen AI applications, and understanding the concepts. ☞ Github ☞ Learn More

Today’s websites are designed first for mobile and then for other platforms, and it is getting important to bring mobile XR functionality into the websites. Google’s scene viewer is bringing WebXR for mass adoption. Theoretically any 3D model can be tried in your space, and you can easily built AR experience for your website. eCommerce has already transformed into mCommerse, and now taking steps into xCommerse (XR Commerce). 3D Model viewer is very common requirement for across different domains, and it will be the basic requirement of developing for Metaverse as well as for any digital business in future.

Accessing native XR features from the device using a web page is another form of WebXR. In this article, I want to share an experiment where I tried to control the android device’s native features such as controlling volume and camera torch from a web page. This use case can be really useful in the XR world, where I can control the feature access in the device from cloud services, even the whole look and feel for showing the device controls can be managed from a hosted web page.

The web has grown from a read-only web (Web 1.0) to interactive web (Web 2.0) and then moved into the semantic web which is more connected and more immersive. 3D content on the web is there for quite some time, the most web-browsers support rendering 3D content natively. The rise for XR technologies and advancements in devices and the internet is leading the demand for Web-based XR. It will be a norm for web-based development.