DEV Community

Discussion on: How about those progressive web apps?

Collapse
 
nektro profile image
Meghan (she/her) • Edited

I've made some comments in the posts you mentioned, they're all great reads. On your point about them being a little Chrome-centric. I agree and disagree. The idea is for all browsers of all kinds on all platforms so that developers that are willing to put in the effort can finally have a write-once/run-everywhere dynamic with the code they write. However, Chrome is the most fully-featured when it comes to a lot of the things most devs would want. I haven't really publicized this much because they don't have Service Worker's *quite yet* but on my website I make a bunch of common use utility PWAs at apps.nektro.net. They're all on GitHub and the reason I bring it up is because in the venture of making those apps and plenty more I plan to make in the future for that project I have come across some browser incompatibilities that make making really good PWAs hard on anything other than Chrome. Now, this isn't to discount any of the work that the other browsers have done. They've done absolutely fantastic work. But, when browser A doesn't have this API and browser B doesn't have that API it leaves Chrome as the only browser with everything.

I keep a running list of some of the common gotcha's that I've run into on the repo but I can list some of them here:

  • Custom Elements not supported in Edge
  • IndexedDB not supported in Edge
  • ES6 Modules not supported in Firefox
  • Lots not supported in Safari private mode

I believe PWAs are the future, and we're sooo close!

Collapse
 
rhymes profile image
rhymes

I starred your repo, I'll definitely take a look when I get to implement a first PWA.

I agree, the work they've done is so important but I think the companies driving the development need to believe in them a little bit more :-)

Crossing fingers