zlacker

>>foxfir+(OP)
I wish Apple and Google would make rules to the effect of "if your app's entire functionality could be done in a regular website or PWA, then you can't put a native app on our stores".

>>joseph+89
> if your app's entire functionality could be done in a regular website or PWA, then you can't put a native app on our stores

A very silly threshold, since this would knock out probably 95% of the app store, including games, since "websites" are extremely capable these days, with full 3d graphics, etc. Then, each time safari added a new modern browser feature, more would get knocked out.

>>nomel+0a
Why is that a bad thing? Wouldn't we be better off with all of them being PWA's?

>>joseph+ya
Gotta love the HN bubble. Users want apps, not PWAs.

>>karanb+5c
If Apple wanted to make PWAs look like apps, users wouldn't be able to tell the difference. Except that's not what Apple wants at all.

>>frollo+Ae
I don’t think that’d be possible without a considerably different web engine than currently exists. Even on desktop with Chrome which is the best case scenario currently, web apps are visibly different from their native counterparts due to differences in things like click handling, latency, etc.

>>cosmic+ik
Most apps nowadays are already websites inside a thin wrapper, and that part is just so it can go on the App Store and have certain OS integrations, not for the UI. Like yeah React Native implements a button with UIButton, but Safari also implements a button with native code.

Good example is Discord. Complex app, only really difference for native is something about push-to-talk.