When writing mobile applications over Flex 4.5.1, your application may be running in the background, even when pressing the back or home buttons on your device. This may become a problem if your application is doing things using timers, making server calls etc.
When developing mobile applications with Flex 4.5.1 you are always going to have a short time until the application loads.
It is very recommended to add a splash screen to your application to ease the wait and improve the User Experience.
Over the past few months, I have heard that question many times.
Deepa Subramaniam, Senior PM for the Flex team, alleviates those concerns with her post (rather a post on the Flex team blog).
It is a must read.
Christophe Coenraets, Adobe evangelist, published a very interesting post about charting on mobile platforms.
You can read more about it here.
Adobe published on Devnet Flash Builder articles a great post with loads of tips and tricks on how to speed up your work.
Some are old but some are new and if used wisely can really speed up your daily coding work.
You can read about it here.
Currently, Flex 4.5 / AIR 2.6 for Android provides a consistent platform for desktop and mobile apps. While consistency is very important there are times when developers need to extend beyond the common APIs.
This article, posted by James Ward on his blog, will walk you through how to integrate AIR for Android applications with other native APIs and functionality in the Android SDK. It covers three common use cases for native extensibility: System Notifications, Widgets, and Application Licensing.
This is a great post that alleviates my biggest concern regarding the usability of Flex as a development platform for mobile applications. I intend to use this information on Tikal‘s next FuseDay, in the session for developing a mobile application over Flex that needs some native APIs.