Six misconceptions about AMP

It is owned by Google

AMP was created by Google and other publishers like eBay, CNN, Pinterest, etc. It was a team effort to make the web faster (initially) and retain / convert more users. AMP is now open source and anyone can contribute to it in Github.

Most of its components are inaccessible

AMP has numerous working groups focusing on things like UX, performance, etc and one of them is accessibility. Each component undergoes an accessibility testing before it is released and they test them after each update. I found out AMP components to be many times more accessible than your average JS library.

It is only used by bloggers and publishers

Initially AMP was created for faster news stories and blogs. Nowadays you can build almost any type of website with it, like e-commerce, online booking, portfolios, etc.

You can’t create a standalone site with AMP

Yes you can! It is encouraged to build your site AMP first, rather than pairing it with AMP. If the requirements permit it, I built all my sites with AMP from the ground up, and this way I don’t have to worry about maintaining two separate versions of the website.

Google is currently working on Bento AMP, which will allow you to use AMP components even if you site doesn’t validate as AMP. How cool is that?

Google will abandon AMP and my sites will die

It is true that Google has buried a lot of projects. However, the core of Google is Search. It will never kill it. AMP is part of Google Search. I am sure AMP is invulnerable. Even if something happens, AMP is open source and the rest of the big companies involved in its development and many developers will still sustain it.

Besides, how many JavaScript libraries and frameworks have died over the years? Too many!

AMP sites are difficult to build

For me it is easier to build an AMP site, rather than an ordinary HTML one. I know where to find the components and I have learnt the development patterns which makes my work easier. Not to mention that the AMP working groups constantly improve the components and the core which your site receives automatically so the cost of maintenance goes down.