Polymer and Progressive Web Apps: Building on the modern web - Google I/O 2016

Taylor Savage on Polymer and Progressive Web Apps: Building on the modern web
The Polymer library, re-written from the ground up with its 1.0 release last year, helps you build composable, interoperable components to use in your web applications. We'll go over the latest features of the library, show how to use some powerful newly-released components, show how Polymer is used in practice, dive into the cutting-edge tools for shipping component-based applications, reveal a brand-new way to get started building Progressive Web Applications with Polymer, and a take sneak peek into the future of the project.
Watch more Chrome talks at I/O 2016 here: goo.gl/JoMLpB
See all the talks from Google I/O 2016 here: goo.gl/olw6kV
Subscribe to the Chrome Developers channel at goo.gl/LLLNvf
#io16 #GoogleIO #GoogleIO2016

[@jerryf196]

I been working on a project for the past 4 or 5 months and learning & developing between polymer and firebase all I have to say is WOW. The added features is incredibly amazing between the 2 technologies which my future web app will be based on. Thanks google team!

[@finncallan1087]

A tip : watch series on kaldrostream. I've been using them for watching loads of movies recently.

[@EugeneKarasev]

I love you GOOGLE! This is almost completely new school of Web development! Excellent presentation Taylor!

[@ryanwarrender6450]

Excellent presentation Taylor!

[@GoadvanzBluetooth]

Very interesting, thanks for sharing info on the Polymer project. Definitely learned a thing or two :)

[@robertocarlosgonzalezflore6700]

I've been using Polymer before the 1.0 version and all the changes seem to be happening at a really really slow cadence. However, great job guys this is a great project and definitely a change of paradigm on building web apps.

[@AnkitMaheshwariIn]

Very helpful - Next generation app! Visionary!!

[@modernator]

This is awesome...

[@jorgeduardoardila]

Great talk, very clear, illustrative and motivating. Thanks Taylor. I agree, frameworks cause overhead and are a liability. I think this talk as well as the notorious scarcity of angularjs talks, are signaling that angular's coffin is being nailed.

[@MrLrodlima]

I don't see this way. Probably Angular JS will survive doing web Apps for desktops. I see a more real threat for Ionic 2.

[@EugeneKarasev]

Agree, Ionic 2 seems already outdated, but Angular 2 will leverage Polymer to decrease dependency on native languages on mobile platforms providing quite similar UX. It is really great strategy, it is really Google flavour.

[@AngelaChapman420]

great video very educational

[@GGAAAFF]

Bien contada la historia.

[@mahabubul-hasan]

wonderful

[@Remindor]

There is a lot of hype about offline usage - While this makes sense for some social apps and online stores, it's not that useful for a lot of use-cases. E.g. If you have a trading app, you do NOT want it to show the user the cached data because the cached data is out of date - In this case, it's better to just show the user an error message informing them that they do not have internet access. Also, recovering from a bad connection with automatic conflict resolution is imprecise - The problem is that you can never establish collaborative intent (with absolute certainty/correctness) when you have multiple users interacting with the same data at the same time whilst they are offline. It is fundamentally impossible. E.g. Maybe user B would have performed a completely different action if they had known that user A performed a specific action a few seconds earlier (unfortunately user B couldn't possibly have known because they were offline when user A performed their action). There are many cases were user B would have preferred to NOT perform any action at all until they had all available information. While automatic conflict resolution is great for some use cases, it's important to note that in some other cases, it can also be downright deceptive for the user - There is no silver bullet and each data/collection in your app should be considered on a case-by-case basis.

[@user-hh8ss5zc5b]

Google makes web better :)

[@rkenne1391]

EXCELLENT

[@unknotmiguel]

How do i put the app on my phone, i mean install the apk is cordova?

[@suryamidha]

What a last name!

[@jerryf196]

So where is this app storage element polymerfire? I do not see it in the polymer-elements catalog. I came across the github account: github.com/firebase/polymerfire but how do we install it?

[@SkinnyCalhoun]

You should be able to add it to your bower.json file as a dependency, e.g. "firebase/polymerfire#v0.9.2"

[@judgewest2000]

The wooping and clapping come DIRECTLY from Steve Jobs' presentations and is just cringy anywhere else