Spotify, The Apple App Store & Why PWAs Rule
▻https://love2dev.com/pwa/spotify-apple-appstore
Comment Apple décourage au maximum le développement des PWAs...
...et pourquoi c’est un combat d’arrière-garde perdu d’avance !
(et avant tout une histoire de GROS sous)
The more I discuss the merits of progressive web applications over native apps with clients and potential clients I have formulated a simple way to determine if you should develop and ship a mobile app:
“Does your app help sell iPhones or generate significant store revenue for Apple?”
If your answer is yes then you should think about developing an app. Otherwise a progressive web app is probably your better choice.
We also know that consumers are tired of mobile apps. Today no one downloads apps anymore. Sure there are app downloads, but by and large the fad has ended. Most app downloads are to new phones, ‘restoring’ a user’s existing apps.
[...]
Right now there are many large brands taking that journey. Uber, Lyft, Twitter and others are in the process of moving to a progressive web app solution. Most have PWAs with feature parity to their native apps. They typically have moved to a PWA as the client code base and use a hybrid wrapper like Cordova to put the solution in the store.
Blocking updates is another major aspect of Spotify’s complaints. I know they are not alone, I talk to app owners all the time that express frustration with long update cycles and rejections. It is a trail of frustration for many.
On the web, you find a bug, fix it and deploy an update as fast as you can. That could literally be a couple of minutes to just under an hour if you have your ducks in a row, and it is not a major bug of course.
I know some sites update 1500 or more times a day. Try that with your native app.
[...]
Good luck doing that with Apple in the way. Developers I speak with tell me they expect 2-4 weeks before bug deployments are actually released in the store.
Voir aussi : le site dédié de Spotify : ▻https://timetoplayfair.com