Flash has long been a taboo subject within the Apple company because Steve Jobs is firmly against its implementation in the iOS operating system. Although users have been asking for the inclusion of flash for a long time in order to be able to watch movies from other sites besides YouTube or to be able to play an online game, Apple vehemently refuses to include flash in iOS- the for iDevices. Apple claims that flash is unsuitable for mobile phones because it requires a lot of resources to work properly, and smartphones are not yet ready for it.
Video clip above is how flash player 10.1 works on a Google Nexus One running Android 2.2 Froyo. You can notice that none of the uploaded videos run at a decent framerate, although most of them are of low quality. More than that, scrolling through the page is very difficult due to the flash content, even though the Nexus One has a 1GHz processor and 512MB of RAM, so the hardware is capable enough to deal with the "Flemish" flash. In conclusion, the flash works extremely poorly on the Nexus One, even though Adobe boasts that it has significantly improved its performance.
When it comes to Samsung Galaxy S and another Google Nexus One, the situation changes radically:
[youtube]http://www.youtube.com/watch?v=5FqNt1dTkRg[/youtube]
[youtube]http://www.youtube.com/watch?v=cb9jfdltkUU[/youtube]
[youtube]http://www.youtube.com/watch?v=hoHpJ8vHloY[/youtube]
So some terminals can load flash content without problems, but others still have problems in fulfilling their duties, even though we are still talking about a Google Nexus One. With the Samsung Galaxy S, I noticed a very interesting thing, when the phone loads a page, it doesn't load the flash content, but instead offers the user the opportunity to choose whether or not to load the flash content. This option "unloads" the processor from the weight of loading the entire content and the pages load faster and the scrolling is more fluent.
Could Apple do something similar for the iPhone? Of course yes. Does he want to do something like that? Of course not.
