Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Fully AMP pros and cons

July 26, 2019

Fully AMP pros and cons


July 26, 2019

More Decks by aggre

Other Decks in Technology


  1. Pros 1/2 • I can focus on application development without

    defining atomically components. • AMP validators know about performance best practices. AMP • I can get good user experience if only care for CDN. CDN • Do you (really) need SPA? It gives us the noticing of asking questions. SPA ?
  2. Pros 2/2 • I could build without any problems with

    just AMP. AMP • I could build without thinking about the layer of persistent state. • When I return to the original means of web development, I remember the issue is simple.
  3. Cons 1/2 • I don‘t know the templating library to

    generate AMP valid HTML. AMP HTML • Insert the boilerplate, styles put together one, and resolve AMP script dependencies… 1 AMP … • I made it myself.
  4. Cons 2/2 • amp-bind‘s states, expressions, and bindings interact using

    strings as keys. amp-bind , , • Is the key exist? Is the schema correct? I need a parser to validate it. • I want to solve this problem by using the JS/TS platform, not a parser. JS/TS …
  5. Insert the boilerplate, styles put together one, clean up duplicate

    styles with cssnano, and resolve AMP script dependencies.