4 ms·

> Ban flash. Biggest competition to native apps That's not why that happened. Flash wasn't "banned," Apple chose not to allow support for it in Mobile Safari f

> Ban flash. Biggest competition to native apps That's not why that happened. Flash wasn't "banned," Apple chose not to allow support for it in Mobile Safari from the beginning. It was never removed or banned. Flash was a dog. Power hungry, slow, inefficient. I recently had to touch the codebase for an Adobe Air iOS app and the runtime is pretty horrific. Adobe never got flash good enough for mobile, and Apple was right to call them out on it. Flash was never any good on Android either. Otherwise it'd still be around. > Cripple the iOS web browser just enough that web apps trying to have native style performance will struggle. Mobile Safari is a good browser. It's fast and is not crippled. It consistently beats browsers on other mobile platforms despite running on often slower hardware. A great mobile web browser is what made the iPhone a great product. > Release their own map to push Google out of their ecosystem. When that didn't work now they are trying this. This is because Apple's contract with Google expired and they had to renew on terms that they could not agree to. My recollection of this is that Google wanted a bigger branding presence on the iOS home screen and refused to license mapping data for turn-by-turn navigation (I believe they wanted the Apple-developed Google Maps application to be branded "Google Maps" rather than just "Maps"). Apple saw no way out aside from investing in their own mapping data and infrastructure.

Joeri 11y ago
Flash was not slow, it's just that flash ads were ahead of their time in abusing the system's resources. The supposed slowness of flash relative to browser api's was a myth, although flash content was bloated, in much the same way that modern web pages are bloated. When flash was killed by Jobs I knew it was just a matter of time until people did the same bad things with JavaScript and CSS as they did with flash, and lo it came to pass.
- eosrei 11y ago
  As much as I didn't like installing Adobe's plugin, I have to defend Flash. JavaScript is just recently getting to the speed Flash had years ago. Flash probably still does vector animations better [citation unavailable]. > and lo it came to pass. Yes! Ha!
- interpol_p 11y ago
  Flash was slow on mobile. Adobe Air is still slow on iOS compared to UIKit or OpenGL.
Kalium 11y ago
Apple wanted turn-by-turn, and Google wanted branding and some influence over the app in exchange. Apple wanted turn-by-turn, but apparently wasn't willing to give up much of anything to get it. So Apple jettisoned Google to do it themselves. Then Apple discovered that mapping isn't nearly as easy as Google made it look when their users were unhappy with a decidedly inferior product.
- interpol_p 11y ago
  Right, Apple and Google really didn't have much of a choice. There is no way Apple was going to brand iOS, which is understandable — that would be like seeing an "Intel Inside" sticker on a MacBook. And there was no way Google would just "hand over" a differentiating feature of Android to their biggest competitor.

Joeri 11y ago

Flash was not slow, it's just that flash ads were ahead of their time in abusing the system's resources. The supposed slowness of flash relative to browser api's was a myth, although flash content was bloated, in much the same way that modern web pages are bloated. When flash was killed by Jobs I knew it was just a matter of time until people did the same bad things with JavaScript and CSS as they did with flash, and lo it came to pass.

eosrei 11y ago
As much as I didn't like installing Adobe's plugin, I have to defend Flash. JavaScript is just recently getting to the speed Flash had years ago. Flash probably still does vector animations better [citation unavailable]. > and lo it came to pass. Yes! Ha!
interpol_p 11y ago
Flash was slow on mobile. Adobe Air is still slow on iOS compared to UIKit or OpenGL.

Kalium 11y ago

Apple wanted turn-by-turn, and Google wanted branding and some influence over the app in exchange. Apple wanted turn-by-turn, but apparently wasn't willing to give up much of anything to get it. So Apple jettisoned Google to do it themselves. Then Apple discovered that mapping isn't nearly as easy as Google made it look when their users were unhappy with a decidedly inferior product.

interpol_p 11y ago
Right, Apple and Google really didn't have much of a choice. There is no way Apple was going to brand iOS, which is understandable — that would be like seeing an "Intel Inside" sticker on a MacBook. And there was no way Google would just "hand over" a differentiating feature of Android to their biggest competitor.