First to OP: Why are you denying users the use of your service by beating this dead horse? Does that really in any way serve your users? The current state of a

First to OP: Why are you denying users the use of your service by beating this dead horse? Does that really in any way serve your users? The current state of affairs with iOS is the context is which we must make decisions. So many of the posts here strike me as useless complaining about the reality on the ground which cannot be changed. You want to hack? Simple - get an Android or PinePhone. You want to share your hacks with friends? Simple - make a PWA. You want to make an app for the general public and don't want to deal with app store bureaucracy? Simple - make a PWA. Your app requires native features? Then learn to navigate the app store approval process. I have several friends and colleagues who have launched public apps. Some went the PWA route. Some went the app store route. All have achieved their mission. It's informative to hear their answers as to their choice. Those that choose the PWA route mostly did so because they already had a web service, and just wanted a good mobile version. Those that went the app store route said in effect that it's not really an app (in the minds of their user audience) if it's not in the app store, and were not already providing some service via the web. Granted this is a small sampling of half a dozen. I would love to have a wider sample to review as I am interested in transitioning from desktop web to mobile app development, and want to invest myself in a good foundation. Does anyone know of a good (and recent) article where developers of successful apps are interviewed and ask to explain their platform decisions? A final comment is this. I think Apple is working to make PWAs a viable choice partially to reduce their approval burden and incentivize developers of "simple" apps - like that of the OP - to go the PWA route.