(I've asked this on Reddit too, but maybe others want to chime in.)
Maybe somewhere in that 10 hour someone talks about it, but let me ask about this problem: Google is big, and has many sides, fronts, faces and eyes; what is Chrome, where is Chrome in relation to all the other web-related, web-facing web-targeted things?
Where is Chrome, Polymer, Angular, and Android compared to each other (and the big Google itself)? Should I wait for Angular to adopt the Chrome PWA guidelines? Should I just wait for the Android team to stop developing the native APIs and focus on the WebView and make the whole Android platform more web-compatible? If now, what's Chrome's thoughts on what these other teams/projects/products/faces-of-Google are doing?
That's a good question that I don't know how to answer clearly.
We are a big company with many facets and no clear web direction owner and also lots of platforms (android, web, assistant etc). Generally, it's lots of groups working to reach users on the web. Chrome works on what it can work on and tries to influence other teams as best it can.
Angular team has been very supportive of the PWA story, but it wasn't clear in this conference for sure.
For those not at the event, we had a large forum area where we had more Google teams (AMP and Angular) and many other browsers have a space to talk to developers.... But this wasn't clear by just looking at the videos.
I think the big thing for me, is we are not going to say don't do Android. We should be clearer on why things like Trusted Web activities help you deliver web experiences with native though and we can keep being clearer about why we think the web is good and how best to deploy on it.
Do you have specific examples? I know we frequently talk about the benefits of distribution and reach of the web in comparison to other platforms including Android.
Usually has to do with remarks on why to bother with native approaches, how PWAs are going to conquer the mobile experience or how doing web is so much better than native.
For the exact wording I would need to go again through the Chrome, Polymer, Angular and PWA talks, so just take it with a grain of salt.
Author here. This question came up several times at the "leadership panel." You can see my notes on questions like these in the article, but I encourage you to pull that video up and just watch it.
Google accepts that they're going to have competing approaches inside the company, and this even has significant advantages. We all just have to deal with it.
Maybe somewhere in that 10 hour someone talks about it, but let me ask about this problem: Google is big, and has many sides, fronts, faces and eyes; what is Chrome, where is Chrome in relation to all the other web-related, web-facing web-targeted things?
Where is Chrome, Polymer, Angular, and Android compared to each other (and the big Google itself)? Should I wait for Angular to adopt the Chrome PWA guidelines? Should I just wait for the Android team to stop developing the native APIs and focus on the WebView and make the whole Android platform more web-compatible? If now, what's Chrome's thoughts on what these other teams/projects/products/faces-of-Google are doing?