 there are a bunch of questions that people have already started asking but before I dive into those few questions I want to ask a few initial questions. One is that how well is AMP being adopted at this point of time? Especially the big companies I would also want to understand that a little bit like say Facebook, Apple's and Amazon's and all those companies that are there are they also adopting it at this point of time and also in the world context how well is it being adopted? Yeah I mean obviously like anyone who's investing in something wants to know like you know who else am I like who else am I working with here and who else is like beta tested this. So when AMP launched about I want to say five years ago yeah I think our like birthdays coming in October or something like that the initial idea was news pages are so slow and they're written with pop-ups and we wanted to solve that problem so we've seen very good adoption like the news ecosystem especially since like initially when we launched AMP we worked with news publishers to gather their feedback so we've seen very strong adoption there. Times of India here in India, New York Times, Washington Post, Wall Street Journal, Der Spiegel, The Guardian like we've gotten most of the top publishers out there and the fact that we have WordPress as a CMS enabled and we even have like we're working with other CMSs also means our reach is higher. More recently we started working with e-commerce companies as well and we've seen very strong adoption there. In e-commerce like there's we do lack some like common component support so for example we don't have a payment a component for AMP payments so that does like hinder adoption but for example what you can do is like create an entirely AMP site and then just have that be non-AMP as well. So we've definitely seen success with e-commerce as well when it comes to like larger companies like Facebook or like Apple etc like they aren't like pushing out content so much right it's like more like apps etc and like we really believe like AMP is more like content forward so like not so much adoption like the Facebook and the Twitter but like Twitter for example will link to AMP cached AMP pages which means again you'll like get that great feeling as well. All right okay so but do you have any numbers in the sense that that because I know Google probably is the only company that can tell most accurately predict the number of websites in the world and therefore I guess they would also be able to most accurately say that okay we have reached one percent of the websites in the world or something like that. Is that something that you can share would you have any knowledge about that? So publicly sharing it I know that the numbers we shared back in like April of 2019 so year ago you can tell that yeah that can be that's a good reference point. That was about in the 30 billions I think 30 billion 30 billion 30 billion of AMP pages or something like that. There are 30 billion AMP pages out there in the world I don't know like how it is right now. Okay so I don't I don't know how to translate that into a person page but okay there is a huge number of AMP pages already out in the world so there are definitely a good number of people who can help out in learning how to implement AMP I guess. The next thing I had is who is creating these AMP components how much is it within the core AMP teams per view and how much is there a larger community at this point of time who's also creating these components? Yeah we actually had our contributor summit and I learned that we had about 1100 contributors which blows my mind like for five years but yeah like we do have a core group of excuse me we do have a core group of AMP engineers excuse me that do contribute to the project and like a large part of the components do come from them but then you'll have someone like Pinterest come and say listen infinite scroll of like being able to see an infinite scroll of pins is very important to us and so they contributed the infinite scroll component uh for example Ali express who has an AMP first experience like wanted said like you know what we don't have a we have like star rating something so we want to contribute a component for that so we definitely have contributions from like all types of industries and like they make up our 1100 number but a large part of it does like come from the core team as well and they're about actually I don't know how many the core team would be sorry that's okay that's okay but there's a reasonable amount of contribution that is coming from outside the core team as well as oh absolutely okay so the next thing that I wanted to ask is that when you said that the developer can easily pick here are some of the carousels which is the carousel that you want that's clearly setting up a further divide between a designer and the developer in the team right so how do you balance the expectations that raise because a designer would want to have their own stake on the website experience as well absolutely yeah um and that's why like we work we don't just like have like a bunch of people write a component like out of nowhere like we have a full product process for it we're like we also research for accessibility and everything um the idea is on the AMP team we want to ship the most unopinionated components so like it should have the basic skeleton let's take a carousel right if you have a back and a forward arrow should have some pagination dots what the pagination dots look like what the back and forward arrows look like customize it to your heart's content right how many slides you want to show like absolutely the basic infrastructure like you should have pagination dots you can remove them if you want like you can skip those we provide you with like the custom components like the custom building blocks that would make up that larger component and then how you style it is absolutely up to you but we also believe that we need to be a little bit opinionated so for example um this this is a very common complaint that we get is like our carousel is statically sized right so if you have different sized images it will take up the same amount of size so they're like no we want it to go up and down but then like but that causes cumulative layout shift so like we we do believe in taking a stance here for the user and after that we like leave like a lot of the customization a lot of the design and being brand conscious right if you're times of India you have a certain brand color you should actually be able to brand all components with that but we will take a few like design constraints and put that just to make sure that we are doing well on these numbers all right so speaking of constraints and complaints because you use both those two words in your answer i i want to understand the impact of am on the different teams that are there so let me just talk if i said we get there are three teams and following this i'll also ask a question by punit in fact probably i'll ask if punit if you're there after this answer i'll ask you to ask your question it was quite relevant ones that you've asked if you divide a website team into the main content team people who decide what is the information that should be going out there people who design which is visually layout wise experience wise what are the factors that we have to consider and people who develop and they probably take decisions around the speed the performance and also how it should be implemented software architecture and so on and so forth for all these three teams if you can tell us what are the things that these teams will not be restricted on or not be constrained and what and what are the things that amp does enable them to do and probably for good reasons amp constraints them to do so let's take them one by one do you feel that the content teams would be any way impacted or have you been hearing feedback from different content teams that hey we want the information in this way or we want this type of information to be there but amp is not enabling us to do that so is there anything like that for content teams no like because we're like an open source team it's always been like oh for example way back when you don't have an accordion right i want to hide this content and then show it later so that kind of falls into visual but it's like very much like people who are like thinking about what kind of content how it's structured on a page like that's like it's an html framework like think about how you want to lay out or think about what information you want to put there and you can you want to structure it in certain paragraphs absolutely go forward like that i think is like the least the most empowered let's put it this all right that's the most empowered the content teams so even i from what i understood and where amp comes in it comes after the contents the content team can define almost freely what they wanted how they want things so now from the design point of view what are the things that you feel a designer should be aware of or vary of that okay then i'm working with on an amp site these are the things i have to accept that i will not be have be able to do but i have these many tools at my disposal so that i can make the designs more specific to the brand specific to the how i expect yeah so this answer will kind of go into like the third group which is developers so for example if you're a visual animator right and you think that the button going big and small and like blinking is really good but we don't like to make sure that animations are performant we only support a certain set of like animations like you can scale you can move opacity you can do like some transforms but if you want to change the background image repeatedly that's something that we don't allow to do because it's non-performance so as long as what you're doing like can be done in a performant way and that kind of like falls on the developers ahead a little bit again like i think like less restrict more restrict on the previous one but still let less restricted than developers but i feel that the answer that you're giving is something that may be very hard for a designer to comprehend or understand uh because uh because what really constitutes as uh impact on the experience or or or what impacts the performance so are there any guidelines around this so one was clearly you said motion animation movements uh those are one thing that you said uh is there a complete freedom in the css aspect of things or in the aspect of all the c other than i i guess the animations i i've heard that in animations also there are certain types of animations preferred over the others so are there any general guidelines on those which can which a designer can easily translate into okay now i clearly understand these are few things that i will not be able to yeah so yeah if you like split it up into like css and animations like since you were talking about animation so chrome has an api called web animations right and the idea is to be able to execute these animations on a worker thread so the ones that they think that they can execute on a worker thread which is um yeah like i said like uh opacity scaling and like certain transforms those you can absolutely do and we like fully support like you can even do those on the first viewport those that they don't believe can be like put on a worker thread we don't like support um especially like in the first viewport imagine like your first viewport is janky you can do it like later on for example if you want to like make a blinking image later like down the viewport uh much down that's fine so that's the animation aspect of things for css um the constraint here is we've like seen people like ship entire like bootstrap files etc and only use like 10 percent of i think chrome did a study that about 80 percent of sites use 10 percent of their css so we have we had a 50 kilobyte css limit saying that a your css has to be on the page so that we're not we're saving you that round trip and b it has to fit within 50 kilobytes per page uh we extended that to 75 kilobytes because we did like some work with uh the folks at work presence saw that a lot of themes like do we need that extra space right so we like extended it to 75 kilobyte but that is a restriction for sure and like actually thank we thank you for like spitting it up that way so the amount of css you're shipping down the wire is constrained but that just means that that's easily dealt with in your bill system right you can make you can have like an entire theme pattern but then your bill system only takes in the css that is needed so as a designer you're still like you're still setting up your same theming or like your same bootstrap infrastructure it's like then you work with a developer to say hey make sure that the one that's shipping per page is like less than 75 kilobytes all right so from what i understand uh if you are uh uh coming from a visual communication design background uh earlier the thing that you used to focus most on is uh what do i need to communicate uh what is the content on the page how can i best uh beautify it in certain ways uh make it aesthetic uh present it well and so on and so forth and from there you used to then uh go on to the developer and said look i've come up with this design you must implement it uh and you almost expect that that will get implemented and i think that worldview has to slightly turn for designers to able to understand that what aspects of design is actually contributing to more number of lines in css what aspects of design is actually uh uh creating uh uh movements in the screen and also more technically if you're actually uh designing animations and all you need to understand which of the animations as what nana was pointing out runs on the main thread or blocks uh the rendering in certain ways uh and what are the and which parts of the animations inside css you have to just carefully understand the technicalities of how css animations work so that you know which other things that amp will allow and vamp will not allow so kind of shifts the lens from pure information and communication to what are the technical uh implications of those designs so that has to be reasonably well understood for designers as well yeah i think the css is like less of a problem especially like i've like i've been working with like for example for amp.dev like our visual designers like here's a bunch of css and we're like okay we'll just we have a build system that takes out whatever's needed per page so i think like with the css is like pretty much this the same unless it is like very heavy and in which case if you as a if you as a visual designer find that your css is not fitting within like that your developer has come back and said this have your developer file an issue on us we want to know about that because in that case like this is information that we need to be taking into consideration right don't just silently take it file an issue on us we want to know about right the last group uh nena developers how how does it impact their work now so i think the biggest change for a developer's mindset is the fact that um up to now developers like they write their own javascript they pick a few components and like kind of hack them together um but now with like amp you have like these html components or like these web components that you're supposed to use and they do the javascript for you so that's a shift in i would say it's a shift in mindset not so much a constraint um which like is anytime you like pick up a new framework you start working in react you start working in angular it's a change in mindset um so i think that's like a shift i wouldn't call it a constraint number one um i think number two is you have to for example how do i express this um i think the fact that um you're like using these components means you also like need to like learn a new bunch of documentation and like how to work with a new kind of framework and i guess that's like just an extension of number one and then the good thing is the one thing you don't have to learn is all about these performance things um you can just like as long as you're like running your page on lighthouse and if you see that an app pages store you you can then just like offload it onto another team and say hey you the amp team your page is slow and like i'm just using your components and then we'll fix it for you so i think like that's like a shift in mindset it's like your performance team is outside your business which is like an interesting switch so i don't think like with developers as as much constraints it's more like a shift in mindset which enables a whole bunch of other things all right okay this kind of nicely ties ties into punit's question punit are you there i'm allowing you to talk uh you can probably ask your question because now you have a very pointed question around uh development and implementation yeah sure uh can you hear me yes hey nana uh so the question that uh i had was that uh so we've experienced uh we've tried amp you know with one of our sites and one of the challenges has been maintaining uh updating the amp version of our pages so obviously we have our content pages that we've been you know maintaining and now we've had amp version of those pages uh now as we update uh you know features around our content pages like the styling the ctas or whatever there's always this challenge of making sure that the amp version is also updated so my question is have you heard this as a challenge from some of the other uh sites that have amp versions and what are your recommendations or what kind of solutions have those guys built into essentially reduce this maintenance effect uh you know yep uh that's actually a great question and like kind of like um picks up on like something else so when we originally um released amp like back in 2015 people were creating paired amp experience as like punit mentioned which is they have their non-amp page and then they have an amp equivalent which shows up in like on mobile surfaces such as search etc um and that's like the much where the majority of amp pages came in the start which obviously meant that you had this dual maintenance cost which means like oh i've added a carousel or like i moved my carousel from like the mid-screen like to the first viewport and now i have to go make that change in amp which is contradictory to what i just said right it's like adding maintenance cost and not reducing it uh which is why um what we've excuse me what we've asked developers to do is and this is not possible for everyone right um is to think about can we just go amp first which means make amp the only way that you're creating content on mobile or on desktop or completely altogether and we've seen a lot of people pick this up for example AliExpress's mobile website so if you go to m.aliexpress.com on mobile it's amp first right it's completely written in amp there's no like oh if i go somewhere like if i if i'm not in search it won't show me the amp page no if you go to m.aliexpress.com or you come at it from search you're still get you're always going to be getting amp the desktop experience is not amp tasty.co which like does a lot of very like interesting quick food videos which are always inspiring like regardless of where you go desktop or like uh mobile is amp first so that's what we've been like asking developers to do that yes maintenance cost of like having this two bases hard and so if it's possible for you think about investing in amp first and that could be like only like on mobile or it could be mobile and desktop um and like and like think about think about investing in that we also understand now that that's not always possible for everyone and which is why we're excited about this page experience announcement because you don't have to like you don't have to feel forced into amp you're picking amp because you think it's useful for you but if for example for any reason you think that amp first is not possible for you such as um what can I give us an example here for example you don't like the fact that like you know it's that if you're being served from google search you will be cached we're now working on solutions where you can say you know what I love everything about amp I just don't want to be cached by google right that's just something I don't want to do because I'm an e-commerce company and like caching obviously is like a nervous thing especially around sale times right you don't want cached information you want to give the most up-to-date information in that case you can opt out of google amp cached and like we're thinking about like adding like flexibilities but like really answer your question in short paired amp comes with like this dual maintenance cost and we absolutely understand and that's like concern we have heard from publishers and that's why we encourage them to think about what pages can like actually benefit from amp and maybe we want to like invest in amp first for those pages so if your article pages are useful invest in amp first for them if your product listing pages are like slow invest in amp first for them it's not a perfect solution for everyone but that's that's the direction we want people to be thinking about okay yeah interesting fair enough at least you know we can discuss internally and think through that may make sense yeah and you have more questions punit please go ahead and ask the other questions that you have yeah sure so the second question I have is primarily around e-commerce so from the content perspective we've experienced that amp definitely makes sense given that you know a lot of our content is exposed on the google discover as well but when it comes to the purely e-commerce sites so when we talk amp essentially you know the head of marketing or the business owner is essentially just thinking about the effort versus gains perspective of the implementation right so we haven't been able to I don't know if this is the right word but we haven't been able to justify or find you know enough case studies or material to make sure that amp would make sense when it comes to e-commerce or e-commerce product listing landing pages as well to begin with you know so I mean I just wanted to pick your brains as to how is the amp adoption beyond the content parts of the website or the publisher or the news which which I understand you know where amp definitely makes a lot of sense yeah um yeah so I'll like kind of summarize what I like said earlier like like you said we've like seen success with news publishers and with e-commerce it's like it's more of a recent effort to like invest in e-commerce um and like something like lacking payment support is definitely um definitely like says okay so we would still have to have like amp pages for product listings but when they're checking out it would have to be a non-amp experience because payments isn't supported so that's definitely like a trade-off to make I think the important thing to us like your marketing team is like you know lay out your conversion funnel and see where are we losing users if for example you really believe that you're not getting like your your your conversion funnel is very small at the start then like you know amp helps like give you that reach that increase the reach part of your funnel and the fact that every page is loading fast helps um experiment and I think the best way to like talk through is always to like and this is this is this is not e-commerce specific advice it's actually just like ab tested like if do you actually see that like you know having a faster page on your particular e-commerce company is actually converting more users so maybe like ab test them like give a certain amount of the population and amp page and the other proportion of like don't give them like an amp page or just give them a normal um your non-amp or like a canonical page and see what is coming out of it right make and as to case studies like amp.dev appropriately being shown right here has like a whole bunch of case studies of the e-commerce companies like especially like a lot of asian e-commerce companies are seeing a lot of success here. Tokopedia I think Nikkei Nikkei in japan is seeing some success with it and a south korean company that I cannot pronounce but you will find it on amp.dev right we are seeing success there but again it's a conversation you need to have uh with your business uh with your business counterparts but where what do we want to improve if we want to improve reach absolutely amp is a great thing if we want to improve if we think the payment funnel is like where people are losing out users amp is not going to solve that for you right maybe you need to add more payment supports and something else needs to be solved all together so having that conversation regardless of what vertical you are is like the first place yeah so uh fair point and you know we did look at a lot of case studies on the app side I think and maybe it's our lack of looking at it but one of the things that we kind of still do not uh grasp enough looking at some of those case studies is the amount of effort that even the initial uh you know experiment would take so let's say if I want to try an amp version of a page and we would of course go gradually around it then you know it is always a question around what is the amount of effort it would take for us to uh do this initial experiment it isn't as simple as right I don't know I mean disabling after for the optional so that's where I think challenges when when it comes to you know at least starting to try and feed the waters around that's I feel very vindicated right now because that's something I've been like raising with our like dev rel team as well as like this is all great but like this like this this pictures business and marketing but it doesn't like convince a development TL or a tech lead or a CTO like how much effort am I putting in am I putting 50 hours am I putting 50 days am I putting 50 engineers that's absolutely something that's missing and it differs from team to team it differs on like what their like MVP prototype is but we've seen that especially if you're using a CMS like once you get like the relevant amp plugin so for Shopify we have an amp plugin uh if you're on WordPress and Magento has a few extensions as well we see that like those absolutely like make it much faster but like converting a product landing page we've seen people be able to do that in just a few days and then like getting the being able to scale that like in a CMS is much easier so we've definitely seen like short turnarounds in like product landing pages very specifically which I think is a great way to like start experimentation but your feedback is very well taken especially by me and I will go ha ha our team and be like we need this information so right thank you thanks thanks for your questions Puneet would like to move to some of the other questions as well uh I mean I mean these are also very uh like practical questions that Puneet was asking but moving on from this I just want to uh touch upon a couple of things that I personally learned about I I was not aware of these things which is the amp optimizer that being one of them and also the fact that uh uh if you put it this way uh is amp optimizer meant if you're not using the sedients so uh you can hear me right yep yes uh so yeah amp optimizer is it is beneficial if you are not being served from an amp cache so the cache will do a lot of this for you will pick the correct image to show it will make sure that the css is minimized correctly it will make sure that like the amp runtime is like not blocking but if you aren't being served from an amp cache so for example somebody comes you at from you from origin then like it then you then you should really get like the optimizer benefits right so uh and also are there amp caches being run by any organization other than google uh you were talking about Bing uh as well so does Bing also run a similar amp cache yeah so I believe Google and Bing are like the two ones that I know of but I'm sure amp.dev has any other information all right and and uh uh do you can you pick and choose where you are cached and where you are not cached if you are cached and if you are not cached are these controls available to you so um each of the both the caches so for example if you're coming from a Bing search it will be served from the Bing amp cache so both at least the Bing and the Google amp cache have like cache invalidation API so for example you can say no uh this has been cached for too long like uh like you know invalidate this cache I want the new cache page both of them have like cached APIs that you can like do do a lot of this with if you're if you're um sorry being served from a Google amp cache um search console also gives you some controls here like for that specific end of things and like Bing has similar tools as well so per cache you can definitely say you know what I don't want to be served from the Google amp cache today but I'm fine with being served from the Bing amp cache but you can't you can't control or there is no is is there any robots dot txt equivalent to say that hey uh because there might be more caches coming up in the future uh and if you're saying that uh the responsibility of invalidation and all is is on you on a developer and you can't pick who all are caching you uh at this point of time then that can be a challenge yep so that's why currently the the way is to like what we would call an invalid amp page so for example just like make your page invalid in some way like do something like put 51 kilobytes I mean 76 kilobytes of CSS and that would like throw you out of like the amp caches because the amp caches are checking for like validity uh we don't think that you should have to do that you shouldn't have to be like 75 kilobytes of CSS add like one more rule that's not how you should go about doing it right so we are working on like adding giving you that support to say for example like have an attribute on your page and just say no cache and that just in opts you out of all the caches automatically like when you just write the page got it and there's one audience question out there is it possible to create your own amp uh own amp cache server and or infrastructure and how does that work oh I don't know I am sure I am sure like I know that for example uh when you're being rendered from um the Google amp cache you appear in what is called the amp viewer I know that you can create your own viewer experience for example um if you are tick tock and you want to start showing amp pages you can like design your own viewer for that I don't know if you can have your own amp cache I'm sure you can uh I can start digging into it while we answer different questions all right cool uh moving on from the amp cache now what are the other questions out there so someone had asked uh does it mean that amp can be used to build the main website rather than separate amp pages along with standard html this is something that Nana has already addressed that that is something that she's giving as as an option uh for you to consider that you can build your main website using just amp or go amp first in a way so that kind of gets answered in this uh there are a couple of interesting questions which why I want to uh ask leader but this is uh related to the amp optimizer as well is there any plan to include amp optimizer for Drupal oh yes uh it's part of our agenda for at least this year uh we need to like prioritize things but definitely uh Drupal, Cloudflare, Docker uh Fastly are definitely like some things we're prioritizing uh Netlify has a has an amp optimizer extension that somebody somebody from the community contributed yeah uh and that's like something that I hadn't put on the slide but uh if you go like if you go to amp.dev they'll like show you what our like roadmap also looks like so good question all right uh okay so this is also gets answered uh there's one question called is it possible to create amp pages using flutter or reactjs or other frameworks so yeah um if for example if you're using react like if you have like if you have like the router level so like if you're using next again you can create like amp pages as well um when it comes to flutter view etc as well like we've experimented and like it's still possible what you're basically doing is instead of outputting html you're saying hey like put the amp runtime and like it's amp component so yeah anywhere where like your template anywhere you're templating it's it's theoretically possible if you have a problem file an issue but all right we have uh so another quick question which has come on my chat which is uh pandu fulvani has asked that why amp on my web it doesn't appear in the SERP search engine results page but amp html valid already in console nor in amp test tool okay i'm not clear about the question are you clear about the question that's there on the chat that that's uh at 11 24 is an abat button yep so it's like yeah why is amp not appearing on my web search i mean it's it's appearing like if they go on origin but not on like google search um but it's like it's showing up in the console or in the amp test tool that's um so what's i can't comment on why it's not showing up on search without like looking at like somebody's search console unfortunately because there's like a bunch of things uh definitely check like indexing or something like that right so this would be very hard for anyone to answer with such little detail so probably you'll have to come into uh zoom ask your question like uh there is another question out there from uh kamran hamid uh who has asked should i use amp for uh all the apps or is is there any specific category like the news pages that i should use amp for and not everything else so i think like depending on the vertical i think a good place to start is like what like for example if a user is uh searching for something right they they aren't going to like click on your home page they're going to click on the article and read it so i think that's a good place to start and then as you like you know as you see the worth prove out it can go to like other pages so like where where where's the user going to comment first that could be article pages that could be product landing pages that could be comment pages for example if your social media platform uh those are like a good place to start and then you should expand if you're seeing the if you're seeing the uplift in like reach or if you're seeing the better like performance improvements i don't want to add at this at this point of time that some of these very specific questions at some some of these things which are very much a discussion uh whether you should do it you should not do it and even some of the questions that punit had asked are we we plan to do a more uh advanced or in-detail conversation of this was more of a overview and introduction gives you a good taste of different things but some of these questions you're most welcome to join a couple of weeks down the line we'll plan a session where there can be more intense debate and discussion around amp and how to implement it uh now i want to move on to some of couple of larger questions that audience has put in and that was definitely there on my uh on my plate as well and this is a question that ambika has asked and i'll start with her question and maybe uh take it from there so she had said that like your point about the core team and others nowadays it's tougher to have an unopinated stance and that is right i agree with that uh i guess amp has been criticized for a gatekeeper style could you tell us more about amp ethics and committee if any and if there are any links out there uh so in this question uh let me first uh just ask the gatekeeper style aspect of things because that has definitely been a a point of concern that everyone says like of course uh amp is a solution for you to just as much or as not as much let me not compare but like just like Gatsby might be a solution that you want to make a fast website here is a set of very good practices put together bundled together for you use Gatsby make all your websites in Gatsby similarly here are a good set of performance things packaging together here is amp use amp but one of the challenges with amp that comes is that uh because there are certain very strict restrictions and the fact that it has to be and one of some of the best benefits you get is because it's coming from google's cases the the cds and all those are and and the fact that the the it is uh led by a large organization which is which really drives what are the benchmarks that we should agree on and and push it through because there are definitely other like the the core web vitals is a very great set of standards that that that you're putting in uh but you'll never say you're always saying that uh we this is something that will prioritize uh we recommend these are recommendations uh but in the amp space they don't become recommendations they become almost like you have to follow this that's when you get the benefits uh or otherwise you don't so nana what's your thoughts around those uh any response to that that's um okay let me break it down by like right so um when it comes to yes so for example um for example uh yeah let's start with top stories carousel right like that's something we talked about earlier like up till now amp who's like this was a space reserve from amp and that's because we believe like at that point anybody who's worked in standards will tell you moving standards is hard it'll take like five ten years getting every browser to agree to like ship at the same time and so this was like our way of like testing out the waters and a lot of this like information about like things how to like make sure things aren't moving about have actually come from like amp like you know leading a lot of this and like i think malta who's like part of our technical steering committee which is something i'll explain has like written a really great series of blogs on amp.dev again which talk about like what are the principles that amp started off with and why they're good and how like we intend to make them scale them to like the wider standards like for example daisy loading in images is something that the amp team has been pushing forward for a very long time and like we're finally getting it five years later right so that's why like um there's it is a little bit more opinionated in that regard and when it comes to like who's actually doing a lot of the work like we we've been open source from the start and now like now we're part of the open js foundation along with things like node for example uh where the open js is like has our has a governing body such as a tsc which contributes to it and like i mean not even contributes it actually literally technically steers our direction and it's nine members i want to say um and it has platforms like pinterest it has cdms like pantheon twitter again another platform that distributes amp microsoft on it um it has googlers on it it has axios which is a news publisher on it um so we have like the widest like breadth of amp developers and like web developers were actually thinking about like what are the problems web developers are facing and how can we solve it using amp and now with like this this launch of like coming soon launch of like page experience it means that whatever technology stack you pick absolutely go for it right you're comfortable in something go for it just meet these like things that are good for users how you do it is like not important to us and like our our idea on amp is to make it the easiest and that means like we'll have to post constraints but so will other frameworks to actually like have you meet it right you can't just ship three megabytes of css and have a good lcp and have a good fid that's hard to do um so i think like that kind of deals with both like i accidentally answered the ethics in the part of it as well right right right that that makes uh that makes sense so from what i understand uh there are a set of good practices that amp is enforcing and the direction in which what google is taking like for the longest time amp always made fast plus seo and by seo every most people meant that we'll be there at the top class and that is where you want to be because that's where you'll be clicked more and that's actively in in in the communication that we hear also it featured in your presentation as well that if you're featured there that that's actually going to increase the number of people who come to your website but slowly it seems google is opening up and saying that okay we you don't have to follow exactly amp but as long as you follow and meet these benchmarks we'll also let you into the top carousel is that that's right uh nana i'm i'm correct that's way of expressing it like page experience in core web vitals is like this threshold to clear amp is a tool to help you jump like so you can clear it so now it's important more people start using uh or meeting these benchmarks what what is the the life of am because at the end of the day the larger community at even today is still the html uh the w3c and and the things that they they are deciding the standards that are getting included there now if a large number of websites look at because search google's search ranking has been a huge influence on the development community to keep improving their websites uh this is the first time google is coming up or at least we are seeing they're coming up with oh here is a solution as well for you to actually meet what we are saying is a good practice in case lots of people start meeting the good practice uh how how long do we feel that uh because jumping on a new technology like amp is an investment and then you have to know that uh well this will actually get keep sustaining itself and if the top carousel is given to everyone and everything is given to everyone then people might start drifting away and then will amp stay there for long so i think as long as developers like in a world where everyone has perfect knowledge and everyone is able to create performance sites there is no future for amp that is not the case that is not the world right and so there'll always be a space for amp to help make things easier uh to help make people who you see ms's and don't like and maybe don't understand performance there'll always be a space for amp we'll just be pushing things like forward like amp might change like right now we're exploring a project called bento amp and the idea is currently you can only use amp components on amp pages so if you like an amp carousel for example it's my favorite component if you can't tell uh you can't use it outside an amp page right it needs to be on an amp page but we don't think that that that there's any reason to do so for example if you as a performance engineer have seen you know what the carousel is like a cause for cls issues and it's a cause for fid like scrolling is working too slowly i've heard good things about amp carousel i'll use it on my page and that's the only amp component i will have on my page right so we do see space for like amp to evolve as like needs are being bad and absolutely like if the more other frameworks are like doing well like the amp team's project is like a user first open web forever right we want to like take everyone up we there be amp great if not we'll keep working with standards bodies like you know make sure that these are incorporated into standard ways as well so right uh i there's a very short question and then i think the final question can be asked by archie who has put in a question and then we'll close off the small question first is how amp is this is asked by anil chaudhary how amp is compared with progressive web apps can amp be a progressive web app and amp both so can you have both a pwa and amp together in one yes uh so there's multiple ways you can think about like amp and pwa coming together so one is for example uh your when somebody comes to your page for the first time it's an amp page so they've gotten a really fast experience your amp page loads up a service worker and every frequent every like consequential visit sorry that's the word is like a pw experience so that's one way of like thinking about a pwa amp approach or what we call a plump we're not very good at naming things plump uh or like another way is like yes it's always a pwa but like instead of rendering html you're rendering amp components so instead of like you're getting like the fast amp components but it's like a pwa shell so there's like different ways of thinking it together and again like i think if you go to the learning page on amp.dev there's like a guide which like paul barkers has written about like how to think about pw amp integration but absolutely you can you can still have a service worker you can have two things like add the home screen etc like things that really make up a great pwa you can do with amp as well okay uh the final question it will be great uh sorry to go a few minutes over time and i hope you can deal with us uh the final question i'd ask arki please ask your question i think that's a great closing question i'll just allow you to yeah now you can speak great uh thanks for the talk naina i have a general question about balancing user privacy versus web performance um to give you some context i worked on open technology for a number of years and i currently help non-profits and activists on front line so i'm really not very comfortable with so using something like amp but like can you comment on how we could have web performance without infringing on user privacy thanks so um in regards to amp along certain two ways one is like just creating an amp page and the other is like creating a page that is served from a google amp cash or a big amp cash so when it comes to creating an amp page right this is these are html components uh just like i mean these are packaged html components right if you take a carousel it is basically a bunch of images it's a bunch of images in a div so the same level of security that you're getting with uh for example just using an html component you're getting with amp baked in um if you have like very specific questions about components let us know absolutely like it's incredibly important we have like we uh so i'll answer it like i'll go back a little our tsc for example has like multiple working groups who like specialize in things i contribute to the ui and accessibility working groups so that's my expertise we have a security and privacy working group which like has people from like different companies whose job it is to make sure that everything that goes into this is like approved by them because they are the experts and make sure that it is secure and it is secure and respects users' privacies because that is absolutely like one of our tenants is user first and that means it should be accessible it should be user forward it should be secure it should like respect users data uh and things like for example as like different countries that create like privacy laws such as gdpr um ccpa in the us um i know brazil's come up with a new one right we're always making sure that our consent system supports that so like we have a component called amp consent which supports all of these as they're coming out as they're coming out right we make sure that we're staying on the cutting edge there so that developers don't have to worry about like thinking about okay it's gdpr is opt in but ccpa is opt out how do i get it to work together right we like deal with all of that for you when it comes to being served from a amp cash again like we don't have any it's like the idea is like the the three p's we associate with uh uh with our cash is privacy preserving pre-rendering right it's it's pre-rendered absolutely to make it fast but it's done in a privacy preserving way like we don't we don't send any user information about okay the user seems like they're going to click on this page so like hey hey go send them ads right absolutely not um it's done in an anonymous fashion and it's like incredibly important and i know that there's like two videos at least on like our youtube page that talk about exactly how we make that happen and there's blog posts to that effect as well so privacy is like absolutely something that's important to us i'm personally a big accessibility champion there are definitely security and privacy champions in the team where it's like it's their day job to think about this all the time but thank you for like asking that question i think it's an important one to like talk about and a good one to write right thanks thanks a lot thanks a lot for answering all these questions some of them were definitely critical questions as well and thanks for uh taking out time to patiently answering all of them uh just i'd like to summarize that what we learn at least from the uh nana stocks uh is that there are several good practices that are there in the world of technology amp is packaging it them for you it's almost like having uh google developers work to fix your own performance issues or if not google at least the amp community working that's probably the better way to say say the amp community working to solve your performance issues your accessibility issues and other other challenges that not everyone can keep up to amp is one way of achieving it and how nana has clearly pointed out uh as long as you can achieve them uh it's uh at least how the roadmap goes uh it the plan is that uh as long as you can achieve them that uh google and every every every other the ecosystem around it wants to treat you equally uh but amp is just a way to get there uh that's uh have i summarized it right thanks thanks a lot thanks and thanks nana thanks uh uh has geek and all uh as a closing of this conversation uh you can uh and anyone can uh come in and and give proposals send in proposals or tell us what you want to hear about in the next few sets of uh cv in this content web series that we have uh we in the next few weeks we are going to talk touch upon technical seo again we are going to talk about uh touch upon voice search uh we are going to do another round of amp discussions uh maybe more from an implementation point of view that people who are getting their hands dirty what kind of challenges they are facing and all uh and we want to have more design oriented talks as well so if if any of you are there uh who want to propose a design oriented talk please go to has geek dot com slash content web slash proposals and put in uh what kind of top you want to have and what to see uh that's all from my side thanks thanks a lot thanks nana once again uh and thanks has geek bye take care have a good night thank you have a good day everyone thank you