Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Developing webapp using Polymer : is it ready for production? or not?

618 views

Published on

Lightening talk material for 2015 Google I/O extended Seoul. This presentation covers those topics:

* HTML5, webcompoents and simple introduction to Polymer library
* Working with Polymer library: is polymer library really ready for the production?
* Current problems of polymer library
* Advantage of polymer library
* Summary

Published in: Technology
  • Be the first to comment

Developing webapp using Polymer : is it ready for production? or not?

  1. 1. Developing webapp using Polymer : is it ready for production? or not? Jeongkyu Shin Lablup Inc.
  2. 2. • From XHTML to WebApp • XSLT / Google Gear • HTML5 and eternal war • webcomponent
  3. 3. Webcomponents • HTML imports • Custom element to extend basic DOM • Templates • Shadow DOM • “Polyfill” • Polymer by Google Inc. • x-tag by Mozilla
  4. 4. • Web “App” • Native Custom DOM element support
  5. 5. http://lablup.com source
  6. 6. Problem?
  7. 7. –Old phrase “Devil is in the details.”
  8. 8. 1. It is too google to be true • Polymer-based project since March 2015. • 0.5 - 0.8rc2 - 0.9 and • We gave up (twice) because it is too hard to migrate between each version • Specs changes like fluid: • OK. Let’s believe one more time! • And our quest begins…
  9. 9. • How hard? • Original 0.5 components are unusable on 1.0 • And is it ready? • Polymer main site is still on 0.5 • Many core functions are still missing • e.g. iron-form-behavior with paper-toggle
  10. 10. 2. Vulcanize • Polymer cannot be used as production without vulcanize process • “Compile process” for polymer library
  11. 11. • It does not work as intended: • Generates broken HTML: did not work with IE • Redundant codes in vulcanized HTML • Different CSS result between browsers after compile • Still too fluid: specs are changing every week • We had to make our own patched compiler / script to work with IE
  12. 12. • And how big is it? • ~600k for common paper elements • —inline-css —inline-script option Code Vulcanize minimize crisper
  13. 13. 3. Polyfill has to fill the ocean • 79 / 47 / 34 / 9 • The number of page rendering during HTMLimports IE Safari Firefox Chrome 79 47 34 9 *Tested with our project (without vulcanize)
  14. 14. Pros?! • One code can rule them all • Polymer+electron = Desktop web app • Automatic (and inevitable) responsive design = Mobile web app • Provides • iron elements (HTML form / behavior elements) • paper element (HTML elements with material design) • gold element (special elements for e-commerce) • google element and • platinum element (for web app features like push / local storage)
  15. 15. Final word • It’s too google to be solid yet • Vulcanizer issues • Rendering issues
  16. 16. Final word • Swim in the ocean. DO NOT swim in the sand ocean. • However, if you prepare for the future web, try it. • And we are working on it.
  17. 17. Have a good day :)

×