Apple has been (I suspect purposefully!) dragging their feet on progressive web app support. There list of limitations is long, but most critically for this app (I would imagine), they can't send notifications and they can't work offline.
There are a number of interesting use cases for PWAs, but part of Apple's fear is (potentially) many of their clients will migrate to PWA only, reducing App Store revenue severely.
Apple also loses all code auditing and screening, meaning they can't ban GPL licensed PWAs like they ban alternative Linphone builds (as they are GPLv2), Signal Private Messenger builds (GPLv3) and only the official developer can build and submit these apps to the app store.
Apple's GPL ban also effiectively mandates these apps having broad CLAs to ensure they can relicense the code for use in the Apple App Store.
The business model is outdated, Safari purposefully being a laggard with no alternatives on iOS will eventually bite Apple in the butt, it is just a question of when.
Both the Music industry and Apple seek to maintain their control and thus their cash cows, but whether that will continue to work out for Apple remains to be seen...
SaaS and Entertainment as a service are the replacements, hence Apple Music and their new streaming service. This is also why AT&T, Verizon, Sinclair and Comcast have spent the last half decade buying media companies.
Why does there need to be a replacement? Apple already sells the hardware and their software (iOS and the preinstalled apps) and makes money off of that.
If I make my app available via my website as a PWA, and all the hosting costs are my own, and don't use any of the app store's services, why does Apple deserve a share of the in app (in PWA?) purchases?
Anyway, the message is pretty obvious: Apple won’t ship anything that’s licensed under GPL v3 on OS X. Now, why is that?
There are two big changes in GPL v3. The first is that it explicitly prohibits patent lawsuits against people for actually using the GPL-licensed software you ship. The second is that it carefully prevents TiVoization, locking down hardware so that people can’t actually run the software they want.
So, which of those things are they planning for OS X, eh?
I’m also intrigued to see how far they are prepared to go with this. They already annoyed and inconvenienced a lot of people with the Samba and GCC removal. Having wooed so many developers to the Mac in the last decade, are they really prepared to throw away all that goodwill by shipping obsolete tools and making it a pain in the ass to upgrade them?
The GPL v3 prevents things like the Novell/Microsoft deal to "patent license" Linux.
The consequence is that Apple can't merely settle to solve patent disputes for any included GPLv3 component, but has to find a way to have the upstream component (and all deviations) have free use of the patent.
VLC was removed because a VLC developer (copyrightholder) asked them to. Specifically, they alleged apple did not have the rights to distribute VLC unless they also allowed users to modify / recompile the software.
There is a way for end users to modify their software now, but I don’t know if it would satisfy that developer. VLC relicensed to make clear they don’t require distributors to do this.
I've used VLC on Apple products (phone, tablet, laptop) for years. I can't remember a time it wasn't available. Do you mean some VLC other than the video/media playing application?
If you have citations of GPLv2 or GPLv3 apps that are in the App Store, I would be highly interested.
As far as I can discern, Linphone is provided in the App Store under a proprietary license, VLC had to relicense as LGPL, and GNU Go is still not on the App Store.
My understanding is that Apple doesn't ban GPLvX code - that doesn't mean other people won't write Apple and ask the app to be removed, claiming the app developer did not have proper copyright license.
I don’t think anyone’s tried it, because it was certainly not allowed a couple of years ago. But the language that the FSF used to point to is no longer there, so I’d like to hope that it might be possible today.
It’s not so much that it’s banned; it’s that because the GPLv3 allows users to modify their software and Apple doesn’t without their developer licenses, you can’t give the user all the freedoms the license provides.
It's pitiful there hasn't been a widely adopted open source notification framework like linux is to OS. Apple and Google both implement their own and it gave them overwhelming power over the app developers. Ironically, this framework may start in China as while majority of the people use Android they have no access to G-suite, apps develop their own notifications and eats up tonnes of RAM, this will neatly solve that problem.
Apple is the one holding up Web Push on iOS at this point, Chrome, Firefox, Edge and a number of other browsers support it: https://caniuse.com/#search=push
The statement is referring to the user, there is no practical "work around" for getting their previously functioning, natively executing application operational again, on a computer they supposedly own.
Pointing out a "work around" for the developer is meaningless, in terms of "hey! they can reimplement it as a web app to bypass Apple's shitty walled garden!" is completely useless to these folks in HongKong right now.
I meant, there's no workaround for getting native software that has the capabilities of native software. If web apps were similarly capable I'd agree with you, but as it stands they aren't anywhere near equivalent.
