Mark posted some information regarding the Flash 10.1 installations/updates for mobile phones. The method seems very similar to the distributable player method that was created last year.
Now about the detection of the player version, looks the same as the web plugin, which lift us from keeping track of Flash player versions in WURFL. I asked Mark if there are cases where the player is installed via firmware/Carriers upgrade, meaning that some mobile phones will get an update only via this method.
One question that comes to my mind is a simple one.
What happen when a new update is available that requires a developer to recompile their content (hundreds of games)?
Also will this installation/method be consistent across different OEM/Carriers?
Alessandro
Hi Alessandro,
The upgrade and install paths are not restricted by the carriers on the whole, there is a move away from this model. With the devices that support 10.1 we’ve found that it is the OEM that controls 99% of the distribution. I don’t expect problems here and the examples that I provided should be consistent with users expectations for their device.
Our own rules around backwards compatibility will remain watertight, with the exceptions for security changes. It is unheard of for developers to have to recompile their code for the web with Flash Player.
By the way, we may still need WURFL for FL4 should it be implemented in standalone mode
Ciao Mark,
thanks for the information.
” … with the exceptions for security changes”, this is one of the issues I was referring to. As you can image it might happen that an update is required by Adobe/OEM and developers are in the middle.
Also, AIR Mobile strategy is another topic which we will debate on other posts!
For Flash Lite 4, it would be great to have more information when is the time, so that we can plan in WURFL.
Alessandro