Making Waves recently released two totally free services for the citizens of Oslo, Norway. Trafikanten (trafikanten.no) delivers real time data on the public transport in Oslo and through development in Flex and Flash we have created two applications that help the citizens to get quick access to this data.
The desktop version is created in Flex with an AIR application as outcome, while the mobile version was based on Flash Lite 2.0 and developed using Flash. Both applications are based on the same design and both applications use Shared Objects to save the users favorite public transport lines. Part from that there are two very different solutions. Both solutions were developed within a timeframe of 70 hours!
Read more at http://mjl.makingwaves.no/
The main challenge when developing Flash content for mobile is to develop on a version that most available phones support. We decided to develop for Flash Lite 2.0 even though we lose a lot of today’s phones. But even phones with Flash Lite support have different specifications and it’s a jungle to find out which phone that supports which commands and so forth… but it is possible J
But the biggest issue with this application was loading XML. Flash Lite 2.x solutions are not very friendly to xml loading. It fills up the phones memory in no time. So the biggest lesson learned is to find workarounds if the first thinkable solution is to load xml data into the mobile phone. Part from that, developing applications for mobile phones is no walk in the park, but it’s really cool and not to hard either 
The desktop version is created in Flex with an AIR application as outcome, while the mobile version was based on Flash Lite 2.0 and developed using Flash. Both applications are based on the same design and both applications use Shared Objects to save the users favorite public transport lines. Part from that there are two very different solutions. Both solutions were developed within a timeframe of 70 hours!
Read more at http://mjl.makingwaves.no/
The main challenge when developing Flash content for mobile is to develop on a version that most available phones support. We decided to develop for Flash Lite 2.0 even though we lose a lot of today’s phones. But even phones with Flash Lite support have different specifications and it’s a jungle to find out which phone that supports which commands and so forth… but it is possible J
But the biggest issue with this application was loading XML. Flash Lite 2.x solutions are not very friendly to xml loading. It fills up the phones memory in no time. So the biggest lesson learned is to find workarounds if the first thinkable solution is to load xml data into the mobile phone. Part from that, developing applications for mobile phones is no walk in the park, but it’s really cool and not to hard either