4 ms·

The power of websites is that they run cross-platform. If your website works on chrome on windows it’ll work (for the most part) on Firefox on Mac and safari on

The power of websites is that they run cross-platform. If your website works on chrome on windows it’ll work (for the most part) on Firefox on Mac and safari on iOS. Apple is against this philosophically because it doesn’t take advantage of the unique capabilities their devices provide. It’s the same reason why Apple stopped supporting flash https://www.apple.com/hotnews/thoughts-on-flash/ https://www.apple.com/hotnews/thoughts-on-flash/

scarface74 7y ago
That’s not true. Back in 2007, Adobe claimed that they could get Flash working on the original iPhone if Apple had allowed them. When they finally got it to run on Android years later, it required a 1Ghz processor and 1GB of RAM and it still barely ran and was horrible on battery life. The original iPhone had 128Mb of RAM and a 400Mhz processor. It wasn’t until around 2011 when there was an iPhone that met those specs. Adobe was always late delivering Flash on mobile from Android phones and Palm phones. It was so bad, that the Motorola Xoom was advertised to be able to browse the “real Internet” because it could support Flash. At launch it didn’t. Leaving it in the embarrassing position that you couldn’t browse the Xoom advertising page that required Flash on a Xoom.
- pier25 7y ago
  This. I developed a number of Air mobile apps back in 2012-2014 and all the blame is on Adobe. Flash was extremely inefficient and Adobe didn't want to invest the necessary resources to properly bring it to the mobile world. Adobe cancelled AS4 (aka Flash Next) which would have made Air a very competitive crossplatform solution. They shifted all its resources into HTML5 to throw a bone to the Flash community and it was a complete failure. https://insights.stackoverflow.com/trends?tags=actionscript-3 https://insights.stackoverflow.com/trends?tags=actionscript-... Don't get me wrong, it probably made economical sense for Adobe but it was a shame.
- dnh44 7y ago
  Also flash player on the Mac was terrible and consumed a lot of energy. I’m not surprised Apple didn’t want it on iOS.
  - pier25 7y ago
    Truth is even if Apple had wanted to bring it to iOS it didn't really have a choice. Users would have blamed Apple for the low battery time.
- troquerre 7y ago
  Supporting all of Apple's functionality was one of the reasons for not supporting Flash that Steve shared in his post, but I think you're right that Adobe not being able to get Flash working on iPhone was the main reason. Thanks for the correction!

scarface74 7y ago

That’s not true. Back in 2007, Adobe claimed that they could get Flash working on the original iPhone if Apple had allowed them. When they finally got it to run on Android years later, it required a 1Ghz processor and 1GB of RAM and it still barely ran and was horrible on battery life. The original iPhone had 128Mb of RAM and a 400Mhz processor. It wasn’t until around 2011 when there was an iPhone that met those specs. Adobe was always late delivering Flash on mobile from Android phones and Palm phones. It was so bad, that the Motorola Xoom was advertised to be able to browse the “real Internet” because it could support Flash. At launch it didn’t. Leaving it in the embarrassing position that you couldn’t browse the Xoom advertising page that required Flash on a Xoom.

pier25 7y ago
This. I developed a number of Air mobile apps back in 2012-2014 and all the blame is on Adobe. Flash was extremely inefficient and Adobe didn't want to invest the necessary resources to properly bring it to the mobile world. Adobe cancelled AS4 (aka Flash Next) which would have made Air a very competitive crossplatform solution. They shifted all its resources into HTML5 to throw a bone to the Flash community and it was a complete failure. https://insights.stackoverflow.com/trends?tags=actionscript-3 https://insights.stackoverflow.com/trends?tags=actionscript-... Don't get me wrong, it probably made economical sense for Adobe but it was a shame.
dnh44 7y ago
Also flash player on the Mac was terrible and consumed a lot of energy. I’m not surprised Apple didn’t want it on iOS.
- pier25 7y ago
  Truth is even if Apple had wanted to bring it to iOS it didn't really have a choice. Users would have blamed Apple for the low battery time.
troquerre 7y ago
Supporting all of Apple's functionality was one of the reasons for not supporting Flash that Steve shared in his post, but I think you're right that Adobe not being able to get Flash working on iPhone was the main reason. Thanks for the correction!