upvote
Who pressured Apple and why?

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

reply
> 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)

reply
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.

reply
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?

reply
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.

reply
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.
reply
answer: adblocking in the browser (and other data scavenging which can be done with native app more easily than PWA)
reply
What “data scavenging” can be done with an iOS app without the user explicitly giving the app permission?
reply
It looks from the cited sources that developers wanted to write apps, Apple chose to do this in a way that allowed it to keep control of what was installed.
reply
This week Bruce Perens (who wrote the original Open Source definition) remembered talking to Steve Jobs about Open Source back in 2000.

https://thenewstack.io/50-years-ago-a-young-bill-gates-took-...

Perens had accepted a position as senior Linux/Open Source Global Strategist for Hewlett-Packard, which he describes as leaving Apple “to work on Open Source. So I asked Steve: ‘You still don’t believe in this Linux stuff, do you?'” And Perens still remembers how Steve Jobs had responded.

“I’ve had a lot to do with building two of the world’s three great operating systems” — which Jobs considered to be NeXT OS, MacOS and Windows. “‘And it took a billion-dollar lab to make each one. So no, I don’t think you can do this.'”

Perens says he later "won that argument" when Jobs stood onstage in front of a slide that said ‘Open Source: We Think It’s Great!’ as he introduced the Safari browser."

reply
That's interesting! However I would argue Jobs sadly won that argument, as there really didn't come any open source os for neither phones or major push on PCs in the almost 30 years since that exchange.

While yes some software have come in that format, it took the big 3 to push the server Linux based clouds, Google to push it on phone, tablets and laptops and now Steam to make a push for the average gamer.

This is not to discredit the work being done outside those lab's which very much build on the work for free or by foundations, however the first versions just don't capture a majority of the available markets which the OSes Jobs mention very much did and the others by the billion dollar labs since.

reply
I interpret what Jobs said as claiming you cannot develop a "great operating" system without a "billion-dollar lab". If so Perens was right.

What has been shown is that it takes billions of dollars to market an OS to the general public.

reply
Less than a year?

Doesnt really sound like Jobs was putting up much of a fight there.

reply
They didn’t have much of a choice. In that time people had already developed jail breaks and Cydia, an app store in its own right, was thriving.

Before Apple’s App Store launched, my iPhone was running all sorts of other apps and alternative launchers.

Apple had to move fast to keep things from getting too out of control.

Over the years, as the vulnerabilities in the OS were closed and iOS added features, the need or desire to bother with jailbreaks and 3rd party pirate app stores dropped. I haven’t thought about it in many years.

reply
So basically, Cydia convinced Apple to make billions lol. Now the app store is the most profitable by far.
reply
deleted
reply
deleted
reply
A PWA on iOS is just a cached web page. Safari remains pretty crippled with regards to the APIs (bluetooth, usb, filesystem, etc...) that make local apps attractive in the first place. Apple is fine with letting people cache web pages, they're not fine with stuff that might displace the app store.
reply
And for that I'm quite thankful, if all the stuff that apps could do were possible on the web it would make the web a far far scarier place than it is.

I avoid apps as much as possible due to all the nefarious tricks they play, even with all the sandboxing and review they go through. Without those constraints, I can't imagine the hell that we'd be in.

reply
Which is fine, for the 90% of people that spend their time on the 70% of common features and interact only with the screen and headphones and internet.

But sometimes people like to do stuff like configure their QMK keyboards or load new firmware for their EdgeTX drone radios or make bootable USB sticks, all tasks that work just fine in easily deployed PWAs on every client platform in existence, except iOS.

For small developers of small-yet-oddball clients apps, PWA's are an absolutely magnificent platform. Write once, deploy once, run... everywhere-but-an-iPhone. It really sucks that Apple's devices are crippled like this.

Edit to reply to this bit:

> Without those constraints, I can't imagine the hell that we'd be in.

Again, that hell is literally every other platform on the planet. It's only Safari that is "protected". In point of fact browser permissions management on this stuff tends strongly to be stricter and less permissive than app permissions, which are much less visible.

reply
Not really, as long as they need permission granted
reply