I did a technical review of what I felt were the major pros/cons of implementing AMP pages:
http://blog.robertelder.org/adding-support-for-amp-pages/
Edit: To save you a click, here are some of the key points:
- You can't use Javascript on AMP pages, but you can put Javascript in iframes or substitute the javascript feature for an existing amp-component.
- AMP pages require that Javascript is enabled.
- In order for pages to pass AMP validation you must include the "https://cdn.ampproject.org/v0.js" script on AMP pages. Furthermore, I believe you are required to hotlink to the ampproject version as I have been unable to pass validation with a locally served copy of these scripts.
- You can't use inline 'style="..."' tags
- AMP uses inline 'style="..."' tags on rendered markup
- External stylesheets are not allowed
- You will likely want to maintain a separate AMP view and a non-amp version of your pages.
- The DOM structure of AMP pages will be slightly different than for desktop pages.
I wouldn't say that I like AMP, but since the world is going mobile I figured I should try to become and early adopter for AMP. In a way, I kind of hope that the AMP projects gets abandoned, but if that happens then I'll have wasted a bunch of time adopting it.