4 ms·

Unfortunately, their PWA "add to homescreen" feature is so bad, it's unusable. I've had to tell my users not to add to the homescreen. For example: sending a P

by judah 9y ago

Unfortunately, their PWA "add to homescreen" feature is so bad, it's unusable. I've had to tell my users not to add to the homescreen. For example: sending a PWA to background causes it to die. For my music player app, this is a showstopper; the audio stops playing. Bringing the PWA to the foreground causes a full refresh. Again, showstopper for my PWA.

coldtea 9y ago
>Unfortunately, their PWA "add to homescreen" feature is so bad, it's unusable. As it relates to audio apps -- not generally.
- chipotle_coyote 9y ago
  Well, it does limit use cases to applications that (a) don't need any background activity and (b) don't need to maintain stateful network connections. Granted, (b) is an issue for native iOS apps, too, but it's something I find mildly frustrating.
Klathmon 9y ago
Also a PWA which is "added to homescreen" actually LOSES access to at least some APIs (I know for a fact that getUserMedia is disabled when a page is added to a home screen). This led to us needing to tell our users to NEVER add the page to the homescreen (pwa or otherwise) or the app will stop working, which confused many and made other suspicious (IMO rightly so, that's such a fucking weird thing to have to specify!)
- thrusong 9y ago
  This is really frustrating to me. Why are PWAs second class citizens when it comes to getUserMedia? Why is Apple perfectly happy to cripple websites when a user has specifically pinned it to the home screen, but allows full featured access in the browser? Are they really worried mobile websites will overthrow the App Store in popularity? Sometimes I really feel Safari is the new IE.
  - Klathmon 9y ago
    So in talking with some Safari engineers a while back when iOS 11 first came out, they say it's a technical limitation (Safari is a somewhat different codebase than the "web views" are on iOS, the webViews being more integrated into the OS), and technically an app added to the homescreen is run in a webView. That being said, it does really suck, and it's something they NEED to get solved before the possibility of taking Safari and iOS seriously in the web-app space happens.

by judah 9y ago

coldtea 9y ago

>Unfortunately, their PWA "add to homescreen" feature is so bad, it's unusable. As it relates to audio apps -- not generally.

chipotle_coyote 9y ago
Well, it does limit use cases to applications that (a) don't need any background activity and (b) don't need to maintain stateful network connections. Granted, (b) is an issue for native iOS apps, too, but it's something I find mildly frustrating.

Klathmon 9y ago

Also a PWA which is "added to homescreen" actually LOSES access to at least some APIs (I know for a fact that getUserMedia is disabled when a page is added to a home screen). This led to us needing to tell our users to NEVER add the page to the homescreen (pwa or otherwise) or the app will stop working, which confused many and made other suspicious (IMO rightly so, that's such a fucking weird thing to have to specify!)

thrusong 9y ago
This is really frustrating to me. Why are PWAs second class citizens when it comes to getUserMedia? Why is Apple perfectly happy to cripple websites when a user has specifically pinned it to the home screen, but allows full featured access in the browser? Are they really worried mobile websites will overthrow the App Store in popularity? Sometimes I really feel Safari is the new IE.
- Klathmon 9y ago
  So in talking with some Safari engineers a while back when iOS 11 first came out, they say it's a technical limitation (Safari is a somewhat different codebase than the "web views" are on iOS, the webViews being more integrated into the OS), and technically an app added to the homescreen is run in a webView. That being said, it does really suck, and it's something they NEED to get solved before the possibility of taking Safari and iOS seriously in the web-app space happens.