> So what do you think Apple should do here? - Support service workers on PWAs that Safari has added to the Springboard. - Support permissions-based model for

> So what do you think Apple should do here? - Support service workers on PWAs that Safari has added to the Springboard. - Support permissions-based model for reasonable user-facing features like background audio and camera. - Don't reload application context when backgrounding PWAs; this doesn't happen if you run the exact same page in Safari-proper. It's really not hard... Apple has had longer than Google to do this right and has repeatedly chosen to not add mobile APIs to Safari until the 11th hour, which only hampers adoption and makes them take longer to get to the 11th hour in the first place. > It's specious to build on a non-native API and then complain that its capabilities and platform integration are inferior to native. It's not, however, specious to compare to non-native APIs on other platforms which is the point of this entire article. > Apple is right to be very conservative with what it allows these apps to do, at least initially. The problem here is that last part, the fact that iOS has severely lagged behind in open web API adoption for the better part of its existence