So Google has two very similar roles, DPE "Developer Programs Engineer" (which I am) and DA "Developer Advocate". Both roles exist within Developer Relations, but we also have Tech Writers, UX folks, ... etc.
Yes! I suppose you saw my post. After the crazy failure we had last year, I have a much better idea of how to build it out this year. Also, I'm currently weighing up whether to drop IE11: global usage is sub-2%, and it would save us a huge burden: I literally would get to ship only <script type="module"> code because that's what all evergreens support.
I'm actually not sure! I think for PWAs to be successful, we have to solve some of the 'gaps' that make folks want apps. I'm often asked at events about access to SMS, Contacts, etc, and this list is huge enough that I'm not convinced just playing whack-a-mole is the right answer. (But I also don't work on standards at all.)
I feel that the largest issue with PWA's is the lack of public knowledge.
On Android users are hit with a popup, something they are trained to ignore. Then if every site pressured you to download its PWA then users will stop caring.
On iOS users are given no hint that it exists without prompt from the site. Apple seem keen to bury them.
I feel the solution would be to allow PWA's onto app stores and have more seamless transitions between the 'APP' and the web
So something you should look at is the onbeforeinstallprompt event. It lets you capture the 'popup' and display it again somewhere in your UI. Controlling this display is a better experience, because you can show it only to your engaged users, in a part of the UI that they'll expect.
Trusted Web Activities are also a way, on Android, to get your PWAs on the Play Store.
TIL! Ill take a proper look at all this.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.