Building a player for Android is not *that* difficult. It can be done and it's not a problem per se... but because Android is NOT the same as Android, things get complicated. Let's assume that telephone producer "A" makes 10 different models of smart phones. We can actually count on there being at LEAST 3 different versions/builds of Android running on these phones. Maybe one of the builds can run Flash, while the other 9 won't. Maybe 3 are with WebGL support, while the other 7 don't have it... etc. Then there is phone producer "B"... and they also have 10 different smartphones... their Android OS will be very different from the Android system of the phones from producer "A".
What is better, Flash or HTML5 .... that is not really a question to be asked. HTML5 is not a competitor to Flash, but rather a platform for internet browsers. Flash will benefit from it, so will everything else. For us, in the panorama field, we have now the Flash panoramas and webkit/Safari browser panoramas. I know of only ONE HTML5 panorama player, and it was made before the first release of HTML5 capable browsers... it was very crude, and there has been nothing done to replace it or build something similar, since it doesn't have a future tied to it. In technical terms HTML5 simply doesn't have what it takes to run interactive content smoothly and easily. If we talk about Flash and Safari/Webkit panos, the answer is very very simple: Flash is by far the superior technology in every way we can look at it.
What can be done in Flash now, is completely impossible to do in webkit/Safari panos.
Playing internet radio in the background and having a "DING" mp3 soundfile to play at the same time (imagine you have a hotspot that is supposed to say "DING" when it is clicked)... can be done EASILY with Flash, but it is IMPOSSIBLE to do in webkit/safari browser panos. Not going to happen. And lets assume you have a pano with a fireplace, using a video showing the fire, and in the same locale there are several candles burning (also videos)... NOT a problem to do in Flash, but completely and absolutely impossible to do in Webkit/Safari panos... it is even impossible to have a video to start playing automatically. The software has the enablers for doing it, but Apple has decided it should not be permitted. It has prompted me to ask myself: How many people have lost their lives or livelihood because of some video files starting to play automatically? ... and I have yet to find one single case that can justify blocking that feature. Thanks for your stupidity Apple!
The iOS player Proggy is making now, will be sold as an add-on for Flashificator, and when people who have Flashificator have purchased and installed it, it will appear as an integrated part of Flashificator. That is the plan in any case. We have not come to that point of the development yet, but it should become like that.
FFC will continue to be Flash based, but when we advance to something different (that is an open possibility), our player software will be known as "The Panorama Player" (www.thepanoramaplayer.com
)... what language it will be written in is still not decided on, but we will move on and adopt to new times as need demands.
If you have iPhone 3Gs or newer, or iPad2 or newer, you can view an example of our iOS panorama player here: http://flashificator.com/ios_player
This is an example several days old, but it is using cubefaces that are 2289x2289 pixels in size, while NO OTHER panorama player for iOS can handle that sized cubefaces. It has been claimed that bigger than (apprx) 1100x1100 pixels can NOT be displayed in iOS devices, because iOS will automatically cut the size in half. So if images of 2200x2200 pixels are fed into an iOS panorama player, the displayed size will only be 1100x1100 pixels. This claim has been touted to be the final and definite truth, but our player showing the images in the maximum possible size 2289x2289 pixels, proves that to be wrong. No, I am not going to inform here and now how this has been possible... Easypano developers might be all too happy to steal the solution and market it as if it was theirs.... as the recent horrible case of them stealing code from KRP shows. So... our iOS player can show panos in GOOD quality, and not the 50% reduced quality other iOS players are displaying now. There will be issues for sure, since iOS is terribly limited in features and permissions, but the resulting output should be a good replica of the original project, but there will most likely be need for some adjusting, and more development on this end to make things simpler and easier over time.
Flash is good... webkit/safari panos suck. Simple as that... but for those who have iDevices, they will be used to the limitations, and accepting those as "perfect functionality".... and with our player, whenever it is published, things will be good, but nowhere near as good as we have things in Flash. That simply is not possible. Flash is the best panorama projection platform ever, and there is no logic in stating otherwise.
Hopefully this helps you to understand the issue.
My destiny isn't carved in granite ...
It's written with a stick in dry sand ... on a stormy day ...