> I struggled with Guideline 4.2 when I tried to publish an app showing the bell schedule and other local information for the neighborhood school.
Why would you not just make this a webpage, and then the users could add it to home page as if it were an app? no Apple review necessary then. What does it being an app give you besides bureaucratic headaches?
The main driver for making it into an app and not just a web page was the need to send push notifications. Of course, I just needed it for myself: hey, it's time to stop working and start driving to school to pick up the kid – "notify me 30 minutes before the last period ends" given that the schedule is different every day; then I just shared it with other parents.
There is a web version (it's Flutter so it was easy to make one), but parents use the app much more often.
Users are /very/ not used to how to install PWAs to their home screen.
Also, in the EU it just opens the site up in your browser, no lack of browser UI like you'd expect. Apple is wonderful.
Edit: It seems I never got the news they reversed course on that particular idea of theirs.
I also have a small private app that technically could have been a PWA.
It’s not a PWA because the UX is just always inferior. Even though we’ve come really far in browser UIs, the browser is still very clunky compared to the smoothness of a native app.
And I like nice to use software.
1. Many people are more comfortable with apps, and don't really "surf the web," and for such people "a webpage" is at best a hassle.
2. Those people and many more besides have no idea what "add it to home page" even means.
It being an app gives those people an experience that matches their normal use of technology, and I think they're probably a majority of users.
Plus, if the parent feels like making an app instead of a web page, who is Apple (or you, or I) to discourage that?