Haxe lives and does compile for IOS on though, the irony (or the power of open source).
I mean you could say the exact same thing for most websites that weren't fit for mobile and touch screen either. It had nothing to do with Flash, it was 100% a developer's problem, not a tech problem.
Flash problems are: proprietary/closed source VM, performances and security, which was all on Adobe side, not Flash developers.
In fact, Flash apps did run on Mobile including IOS via Air. https://www.adobe.com/products/air.html
So Steve Jobs was wrong initially. Let us remember that Jobs didn't want native apps on IOS, he wanted people to write web apps and Native apps to be solely the prerogative on Apple, until he changed his mind. Now you be that Apple prefers developers to write native apps, since it makes Apple a substantial amount of money.
Adobe just couldn't get it done.
This is what disruption is like. It's great that we have orgs like IA doing the work to keep this old content alive and accessible, and a platform like the Web that can grow and adapt over time.
They should have fully open sourced it, at least the runtime.
> They should have fully open sourced it, at least the runtime.
Rumor had it that there was code in there that Adobe (or more likely, FutureSplash) had licensed and couldn't release.
There is also the possibility that the licensed code would have been trivial to work around, which ironically would have created more liability for Adobe due to the mind-boggling stupidity that is "software patents" (in theory, software patents claim a specific implementation, but then in practice are often used to shake down anyone who makes a different implementation of the same idea, and the simpler the idea behind the patent, the worse the problem gets, unless you can find prior art to invalidate the patent claims). All of which would have put Adobe in a tough position, since they are fairly pro software patents.