3 ms·
Until the iPhone came, I've a seen lot of attempts to : - move Java to a more browser friendly position - make Flash lighter, faster and easier to integrate o
by hrktb 12y ago
Until the iPhone came, I've a seen lot of attempts to :
- move Java to a more browser friendly position
- make Flash lighter, faster and easier to integrate on mobile
These were for feature phones, and any of the above were realistic and plausible (I did actual projects using each of the above)
Flash got killed because it was too mouse centric and there would be no bridge between mobile and desktop, thus denying any network effect fom the desktop. The API was good enough, there was a few open source compilers and the runtime was OK. Compared to native Java it was actually nice to use.
But when you see the iPhone or the android phones, there is no compelling reason to do a lightweight Flash app when the same can be done in JS for more or less the same effort (and the js would work everywhere). Access to native functions could have been a selling point, but even that, going the full native route would be more sensible.
TLDR;for me Flash was killed by js coming to mobile, more than anything else