There seems to be some confusion about what AMP is and what it’s used for. There’s a lot of misinformation appearing in this thread and all over the internet, and it might be helpful to go straight to the source to see what’s really going on with AMP.
Hopefully we can get the conversation started here about why AMP isn’t a good fit for the vast majority of websites that are developed on Webflow. There are a few things that need to be cleared up about AMP:
AMP forces all styles to be inlined. You cannot even reference an external stylesheet unless it’s pointing to a custom font. This is game over for any type of visually rich design.
Google itself writes that “AMP is a way to build web pages for static content that render fast.” They’re talking about online publishers of things like news content, and other visually simple webpages that need to load very quickly on mobile.
Down the road, can we expect AMP to be useful for static content sites in certain industries? Sure. We’re already seeing amazing results with The Washington Post and The Miami Herald and other giant publishers pushing specialized AMP content to mobile. But for right now, it’s not at all a good route to take for visually-rich, responsive websites.