8 ms·
This also servers as a warning for PWAs: despite all the hype and virtues (real or perceived), your are at the hands of very fickle gods
by dmitriid 7y ago
This also servers as a warning for PWAs: despite all the hype and virtues (real or perceived), your are at the hands of very fickle gods
- webappguy 7y agoWe all are at the fikle hands of Apple and Google sadly.
- cromwellian 7y agoDon't you have the same problems with native? It's like like no OS update ever broke apps, or that Apple doesn't capriciously remove APIs, or reject you from the app store sometimes for unexplained reasons. Hell, people get broken by OSS ecosystem libraries a lot.
- webappguy 7y agoWish Apple and Google would put more browser collaboration time in, for the benefit of all..constant one upmanship hurts both and millions of man hours in bugs, pollyfills, API repairs, and on and on. Webview, WKWebview teams need more rigorous standards and safety checks clearly for consistency and reliability. Progressive development benefits both. Web-apps are a critical, large and important part of the app developer ecosystem.
- dmitriid 7y agoYup. In the end you are at the mercy of whoever controls the platform and its development.
- tsimionescu 7y agoTrue to some extent, though I don't think there have been many OS updates which deleted all storage for all apps (well, moved to an inaccessible place)... This really is a massive failure of QA and dev.
- tehlike 7y agoThat's cynical. You must have your own bugs every now and then. This is no different. PS: google employee, used to work with torne every now and then, but no stake in the conversation anymore.
- dmitriid 7y agoCynical? Yes. Is that the state of the world? Yes. Browsers are platforms that are as complex as OSes these days. And any bugs or changes in how they work will affect you app if your app is PWA. - It could be Chrome breaking audio: https://danshumway.com/blog/chrome-autoplay/ https://danshumway.com/blog/chrome-autoplay/ - It could be Chrome breaking LocalStorage: this discussion - It could be Chrome removing support for a web standard that was implemented and shipped: https://www.chromestatus.com/feature/4642138092470272 https://www.chromestatus.com/feature/4642138092470272 I'm linking Chrome issues here because Chrome is the most visible of all browsers with the largest marketshare, but other browsers have their issues, too.
- bzbarsky 7y agoJust to set the record straight on the part I'm familiar with, "Custom Elements V0" was never a web standard. It was a proposal, which Chrome implemented and shipped without getting everyone else on board, and which turned out to have significant enough problems that a somewhat different thing got standardized and shipped in all browsers ("Custom Elements V1").
- dmitriid 7y agoOnce something is shipped, people will rely on it. For example, quite famously, Youtube did for a very long time (until this year IIRC). AMP used to use it. There are several polyfills available. Several Polymer versions targeted v0. Etc. etc. It's not specifically Google's fault that they are removing support for these, but, once again, that's the state of the world: browsers are lrage complex platforms that may and will break your app.
- 7y ago
- C14L 7y agoThat's not just true for PWAs. That's why offsite data backups are a really good thing.
- anticristi 7y agoIndeed, I don't mean to downplay the frustration of the developers and their customers. However, valuable data should really not be kept on a single mobile device, which is prone to damage, loss or stealing.
- the_gipsy 7y agoWrong. Relying on being allowed on some appstore is much more like being "at the hands of very fickle gods". Pray that apple/google don't suddenly change their mind and lock you out, because it competes or goes against whatever new trend they adopt this year.
- swiley 7y agoOn sane OSes native is nice. On most consumer OSes I honestly would trust the chrome developers to be more well behaved.