If your client is interested in Accelerated Mobile Pages, get it in writing and include a fee for undoing AMP if they don't like it. If you don't update Google's AMP project cache directly with a special URL for each and every blog post and page URL you AMP, Google holds onto the AMP page in its SERPS and CDN for eternity! Even doing the reminded and manual URL update, this stuff can still be around for a month. Ugh.

Wanted to discuss about this AMP framework by Google. I have developed with it for my company and have been having mixed feelings about it.

On one end, it gives you the power of Google cache, declarative layout and all.
But still, it seems to be too restrictive and filled with bizarre rules that often could have been avoided if they just made guidelines for normal "web pages" to be better and not yet another framework to build "AMP pages".

One more (and probably the biggest) thing. AMP is Open Source... But can it be really considered Open if the biggest player in its development is a single corporation?