Intro to AMP (Accelerated Mobile Pages)

If you browse the web on a

mobile

device today, you expect rich graphics, smooth scrolling, fast animations and transitions, all loading quickly and the good news is that at the platform and browser level we are making great progress towards faster and smoother websites, However, the bad news is that even with these improvements many websites still won't magically become fast experiences, I mean, think about it for a second, you're at a bus station and you click on a link in your Twitter account, You wait five seconds, you wait ten. You keep thinking it must be amazing content if it takes so long to prepare and at that moment you come back to reality, a full screen interstitial asking me to buy sunscreen, a dialogue please like, add, set, distract from the content and makes the page very slow. you can't even scroll and as if that's not enough a bunch of analysis scripts competing in the background are having fun every second and draining your phone's battery or maybe the analysis scripts just want to save the phone from suffering and turn it off. their music quickly, I really don't know in all seriousness, although all this wouldn't be a big problem for the editors of those sites if you were just willing to continue suffering but you don't, you are furious about the current state is so furious that, either you don't bother and click, and studies suggest that forty percent of users abandon after just three seconds or you decide to install an ad blocker, clicking close is a lose-lose situation, you're frustrated because you did not do it.

I can't read the article your friends posted and the publishers are frustrated because they didn't get the chance to show you other cool stuff and relevant ads to help you pay to create that free content and ad blockers may work for you as a reader, but I'm the business model of many publishers who rely on ads to help pay for the content offered, but this is what publishers are obviously not deliberately trying to slow down

pages

- they add all these extras to try to increase the monetization of their site and attract every They turn to more readers to help keep the site running and then end up in this difficult situation where they feel like they need to decide between improving the user experience or focusing on monetization and user acquisition.

These overloaded and user-unfriendly websites are not new. problem and some have tried to find solutions. The former are walled gardens that tie you to a specific content distribution platform. Now you have to implement a custom solution for each platform, and your content can't be discovered through search engines or linked to from others. websites, goodbye to the open web or you could create a native app and lose even more advantages with web offerings, such as effortless entry without installation or easy distribution of content, it is not very attractive, or we felt this was a problem I needed a simple and elegant solution, a new way to implement and ensure beautiful, optimized and content-rich web

pages

quickly and without all the extra clutter.

It is based on the openness of the web and does not attempt to replace it. Allow everyone to participate and collaborate. Publisher platforms and developers support and Profit from that app, short for Accelerated Mobile Pages. The amp project dramatically improves the performance of

mobile

sites on the web, often to the point where they appear to load instantly. It is an open source initiative that is based on existing web technologies and is built in collaboration with many different partners, many technologies today come with super complicated build processes, but that is not the case with &; in fact, an amp page is just a normal html website with a couple of restrictions and extras, no build process, no extra steps, so it doesn't require a lot of extra work unlike having to create custom maps and products for an wide variety of platforms and social networks;

In fact, if your website doesn't use custom javascript and is mostly static, you probably don't even need to create a second version for amp. Each amp document includes the mjs javascript library that delivers optimal performance by adding and validating some important rules in your markup. . When you look at an amp document, the biggest difference you see is that some elements like the image tag are replaced with custom elements. To ensure you stay on the fast track in two critical situations, first allow mjs to control the entire freight chain and prioritize certain items and requests over others.

In practice, this means that most third-party content and elements below the default are loaded after the main content arrives. Your users can start reading as soon as possible. Second Amps custom properties strictly require that the width, height, or other attributes that define the aspect ratio be set. This way mjs knows exactly what your page will look like before the resources are loaded and can lay out the page in advance, this avoids the famous flash of unseen content, the ugliness of a half-loaded website that then starts to skipping while loading more things, as well as the need to re-render and perform additional layout calculations, a browser that performs task tasks can be very slow under any and all limitations. o addition to the amp docs is carefully designed to increase page 211 speed and implement Rail, a user experience-focused performance model that the Chrome team came up with and, because mjs comes with a validator built-in crashing in the console, ensures developers stay in the fast lane as there is nothing more frustrating than the speed regression you discover months later on a page amp, content is always king and user experience is the queen, no compromises, but if now you say wait a second, it sounds great for users, but how does this help publishers consider that users love fast content & allows platforms like google twitter pinterest or linkedin know for sure that this content is fast and then can they promise it to users in return if I know it only takes me five? seconds to read that article I do it much more often with many more articles.

I'm happy that the platforms are happy because I'm happy and the editors are happy because they can show me more content and then everyone wins, start writing. Get your first amp page today by checking out the tutorials in the description or head directly to amp project org for more information.