 Hello, everyone. Welcome to the talk. Myself, Bhanu Shukla, I work as a UI engineer at Flipkart and we are a e-commerce company, biggest company in India. So my talk is on accelerated mobile pages. So basically, we have been trying to revolutionize and make the web faster for all. And we keep looking for the ways to do it. And accelerated mobile pages or AMP in short is what we have come to. Please, next slide. So yeah, AMP is an open source project initiative aiming to make the web better for all. And it is basically, it enables creation of the web pages which are lightning fast. And with AMP, the promise is that the pages will be loaded instantly. Please, next slide. So what is AMP made up of? AMP is basically three things. It has three components. One is AMP HTML, which is a subset of the standard HTML that we have. And it gives us another set of tags like HTML, AMP, which makes the servers readable as an accelerated page rather than just a normal page. Then there is an AMP JavaScript, which is for resource loading. And the AMP cache, which are like the cache servers. So the AMP pages are served directly from the, and mostly these servers are Google cache servers. Next slide, please. So yeah, please, yeah. So what it offers? It offers us a tremendous increase in performance in terms of a huge decrease in load times, which is around 75% in some cases. And data usage is also reduced by 10 times. Owing to the above two, as we know, if we take care of the above two, we will definitely have increased user experience and engagement. So the media outlets are going pretty high on the AMP's. And they have mostly adopted it because everybody wants to be at the better search results options. Please. Next slide. So AMP has already got a pretty good adoption. We already have 1.5 billion AMP pages out there in production already. And it has adopted very widespreadly. And even though it has come to the party after the Facebook Instant Articles and Apple News, but it has gone pretty huge. So there are a lot of criticism, as we are here at the Open Tech Summit. The criticism is mostly about that Google is using to shape how the mobile web works, and in particular to ensure a steady stream of revenue for themselves. But if we take the Google's point of view, they don't claim it as a proprietary and they have moved it into an open governance model. Next slide, please. So is it really necessary to adopt AMP? And so if we see that Google is now the leader in the search market with having covering the almost of the market share, and to an extent that we have the term Google it in the Oxford dictionary. So to stay ahead of the competition, it becomes essential for content-based platforms to have AMP pages and all the customer-facing companies to have the AMP pages to have a better search engine optimization and search results. And most of the media server outlets have already gone to serve the AMPs. Next slide, please. So is it disrupting enough? Have we gone what we are getting with this? So the project is open source, and we are aware about the Google's dominance in such a space. So basically, it doesn't go well with the dev community because the open source is open source. So we as open source developers don't want to be dictated and told that we should write certain things in certain restricted way. We want to have our own freedom. But yeah, so it almost dictates how the way HTML should be written. Thank you. Thank you.