zlacker

>>janand+(OP)
Haha, excellent timing:

I opened HN just now because:

1. I got tired of waiting 2h for my app to get notarized because

2. I can't sell it on the AppStore in the EU... because

3. the AppStore Connect page gets stuck at their DSA compliance form (it's been 10 days).

And, to add insult to injury, the whole thing could be a PWA, without any compromises in the UX whatsoever.

I misread the title, but I still posted this comment as an example of confirmation bias* in the orange book for posteriority. Time to step away from the computer!

* (sunk cost fallacy)

>>rpastu+79
I use PWAs on iOS and they're pretty great. That was the original plan for apps on iOS, before Apple was pressured into creating an app store.

>>epista+yb
Who pressured Apple and why?

I had nor even heard of app stores before then IIRC unless you count Linux repos.

>>graeme+Oc
> While originally developing iPhone prior to its unveiling in 2007, Apple CEO Steve Jobs did not intend to let third-party developers build native apps for iOS, instead directing them to make web applications for the Safari web browser.[10] However, backlash from developers prompted the company to reconsider,[10] with Jobs announcing in October 2007 that Apple would have a software development kit available for developers by February 2008.[11][12]

https://en.wikipedia.org/wiki/App_Store_(Apple)

>>epista+ad
And the irony of this is that a lot of the apps in the app store are hybrid apps that are basically web apps with a thin native wrapper around them because it's just so much less of a hassle to develop for both iOS and Android that way and because, if you're coming at it as an outsider, Swift is such a ball-ache to deal with compared to other languages and stacks.

So PWAs would have been more than fine but, unfortunately, that ship has long since sailed, and Apple make way too much money out of the app store for a course change.

>>bartre+fe
It came out in the Epic vs Apple trial that 90% of App Store revenue comes from in app purchases of pay to win games. The only money Apple is making from these “could have been a web app” apps are for things like Uber where you can use Apple Pay (not in app purchases)- that has the same credit card fees regardless.

If it’s only mean old Apple, where are all of the great Android PWAs and why do developers decide to make native Android apps?

>>raw_an+Tl
Nah, the hyrid thing has been a big deal for a long time. PhoneGap/Cordova was all the rage in 2012/13 when I was working in that area, and I even went to a VSIP event hawking our Visual Studio hybrid development solution.

Once hybrid became possible it was immediately clear that it was the easiest way to get a decent quality app deployed on both iOS and Android. It was a big enough deal that around the time I attended that VSIP event and then PhoneGap Europe, or perhaps shortly afterward, some backlash against hybrid started off with a few big companies trumpeting about how they'd started off native, gone to hybrid for a few years, and were now going back to native again (principally for native experience and performance reasons).

But I think the pressure has always been in the hybrid direction, particularly if you're resource or budget constrained and need to target both platforms, or the web is your main platform (whether than be mobile or desktop). I'm sure the Epic vs Apple fight didn't do any harm, but I don't know what real difference it's made.

The reality is that maintaining two native apps plus a web app is a pain in the ass, especially when you realise Swift - whilst a good language - is a wrapper over some decidedly tedious APIs and a lot of Objective C legacy that you probably don't want sucking up a lot of time. If you want/need apps, it's so much easier to stick a native wrapper around a responsive web app, and that will work well for so many use cases. Not all, by any means, but most SaaS, LOB, or CRUDy apps will do fine as hybrid.

>>bartre+bT
I feel like “web wrapper” apps aren’t super popular nowadays. Most apps are either fully native or use something like React Native, that renders with native widgets.