Roadmap to Polymer 1.1

August 25, 2015 10:42 am Published by Leave your thoughts

TL;DR: We will make Starcounter compatible with Polymer 1.1 starting from the release on 1 October 2015. This will break apps that use Polymer 0.5.

At Starcounter, we have been merely recommending Web Components including Polymer for more than a year now.

Web Components are a standards-based way to build web applications in HTML, without client-side glue code. We are thrilled about easy they make to write server-side apps with logicless rendering in a web browser. You just drop a single line of HTML to import them, then another line to use them – and that’s it! No previous web platform technology allowed for such level of concise yet expressive coding.

On top of that, Polymer is a lean yet expressive library that allows us for easier authoring of Web Components. Though it is not absolutely required to build Starcounter apps, we use Polymer in our sample apps, tutorial, guides as well as recommend it to developers.

At Starcounter, we created a bunch of Web Components to make app authoring easier. The list is long and includes starcounter-include, imported-template, puppet-client and a dozen of others that we keep under the brand Juicy.

Most of our Web Components use Polymer 0.5 as of now. In May this year, Google has released Polymer 1.0, which is a complete rewrite with an order of magnitude better performance and smaller footprint. We have been reluctant to change because of the amount of work involved, but we believe it is the right time to upgrade to Polymer 1.1 at Starcounter.

Our current intention is to switch to using Polymer 1.1 on 1 October 2015. We will publish a preview version of Starcounter and the apps few weeks earlier. Our recommendation is that all app developers prepare for the switch by upgrading their usage of Polymer as well.

As you upgrade your way out of Polymer 0.5, you might also consider migrating to plain Web Components instead of Polymer 1.1. This is what we will do in some of the cases.

Feel free to reach us in comments or in GitHub thread #2854

Categorised in:

This post was written by Marcin Warpechowski

Leave a Reply

Your email address will not be published. Required fields are marked *