Why you might want to use Amp
Currently working on a blogger template that is completely stripped down to bare bones to setup a AMP site. This just a list of reasons why you start using AMP at least for maybe for blogs which I'm more interested. I wouldn't recommend for business sites just yet. Unless you're site is very simple and straight forward or mostly middler-tier based anyway.
- Everything in a AMP site is styled directly in the beginning of the site, no external stylesheets (a huge performance boost).
- Global styling forces developer to think globally about their styles. So the styles run more like a style guide.
- Styles are limited about the total amount for AMP making developers to do more with less.
- No inline-styles this is a plus because there is no surprises for other developers jumping in or modifying (look at cons).
- Possibility of better indexing and page ranking!
- Amp's forced css, there are some css styles that AMP looks for and are required in your application.
- Components are limited to what the AMP team creates, like my first point this could be a major problem.
- Forced CDN, you must use their cdn. So you can use a local version of the files.
- No inline-styling, which is faster and I know some might say too trivial compare but those same people probably said minifying css was too trivial as well. So I don't really care about this one just that I find it odd that the framework prevents it.