Earlier this year at AMP Conf, we introduced the developer preview of . Now we are announcing the general availability of . It’s an AMP component that runs…

We’re excited to announce our solution for arguably the biggest issue affecting Accelerated Mobile Pages (AMP): the inability to use real origin URLs when serving AMP-cached content.

Let’s talk about Accelerated Mobile Pages, or AMP for short.AMP is a Google pet project that purports to be “an open-source initiative aiming to make the web better for all”. While there is a lot of emphasis on the official AMP site about its open source nature, the fact is that over 90% of contributions to this project come from Google employees, and it was initiated by Google. So let’s be real: AMP is a Google project.Google is also the reason AMP sees any kind of adoption at all. Basically, G

Contributor Kris Jones explains why having a responsive web design is a great first step but combining AMP with a PWA design is better.

Your AMP pages have a higher than usual bounce rate? Don't worry, your data may be wrong. In this article, I explain you why.

The following is a guest post by David Attard of DART Creations. David is going to introduce us to AMP (no idea what that is? read on) as well as how you

Google noted in a blog post that its Accelerated Mobile Pages (AMP) project, aimed at hosting and delivering fast-loading content to mobile devices from numerous publishers, is set ...

New Google thing, aimed at unsucking the "mobile" web:

The AMP web component framework