The “Project Fugu 🡠and You” meetup at #GoogleIO is happening in roughly 45min from sending this tweet. https://t.co/NKbzoBXfxq. Join @fractorious, @Vincent_Scheib, and me and hear what an Engineer, a Product Manager, and a Developer Advocate want to _
@jamest_lu @ChromiumDev Oh, that’s a way to visualize the Web API landscape that I haven’t seen before. Thanks for sharing!
@jeffposnick @mhartington Yes, if this actually should become declarative sugar on top of imperative service worker registration, it needs to be clearly specified when the registration happens (and probably even be configurable via attributes). Not sure i
@mhartington In the end for a PWA you need a Web App Manifest anyway. But I can see how decoupling them may be useful for apps that purely use a service worker for performance reasons, but have no intention of becoming installable.
@SCRWD @LinkofHyrule89 @ChromiumDev Yepp. Just like Fugu fish. Always cut it right.
@ChromiumDev If you joined in live, you saw me have “fun” with service workers 💷, if not, here’s the recording: https://t.co/gXX7Aru3Di. The codelab link is here: https://t.co/YStXySRHrq. I’m happy to answer questions on Project Fugu 🡠or anything e
@LinkofHyrule89 @ChromiumDev I also like this explanation :-)
@LinkofHyrule89 Thanks for baring with me… The finished product ifugu-greetings.glitch.meDO.
🔢 In less than 1h from sending this (10:30AM—11:15AM CEST) you can join me for my #GoogleIO workshop on A Whirlwind Tour Through Project Fugu 🡠APIs: https://t.co/AHmS5pAvyE. Registration is optional, but when you do, you get to ask questions (see
@mhartington Or maybe what you actually want is the `”serviceworker”` memeber back in Web App Manifest? https://t.co/mKFyYm6D59
@AltReptile @mgiuca All it does is determine how links should be opened (for example, in a new or in an already open window of the PWA).