5 ms·
The plan was always web apps, they're vastly more secure than any other option. That's a significant part of why safari for windows ever existed. The problem w
by olliej 3y ago
The plan was always web apps, they're vastly more secure than any other option. That's a significant part of why safari for windows ever existed.
The problem was developers just wanted to write native apps, presumably believing that the only secure apple platform would be converted to the Mac-like experience, complete with malware, etc.
So with no one making actual web apps, in part because the web standards of 15+ years ago were not as powerful, and in part because developers all thought web apps were bad, and ongoing "we want real apps" noise, you got the initial UIKit APIs, which lacked _a lot_ of functionality, and made a lot of things very hard.
Or you can just go all conspiracy theory and say "they would never change their plans in response to market pressure, who would do such a thing?"
- jandrese 3y agoAlso, although the original iPhone had a full browser, it was pretty slow. Not only was the data slow, but the phone itself was hamstrung by insufficient RAM which caused way too much swapping on complex webpages. Making a webapp that performed adequately was difficult to say the least.
- grumpyprole 3y agoFurther evidence for this is that Apple ported their widgets, like stocks and weather, to native apps instead of using the web-based ones from OSX.