- Use assets swf instead of swc to have faster startup time.
- Always use splash screens.
- Use Tweener for animations instead of the one built into flex.
- For View based mobile applications, create your own implementation of ViewNavigator than the built in one, as it is slow and heavy.
- Create your own View Manager than relying on built in ViewNavigator as it doesn't cleanup memory properly which is utmost necessary for your poor mobile app.
More Readings:
Hello :)
ReplyDeletewhat do you mean by "Use assets swf instead swc" ? assets is sounds and images ? no ?
Thats correct. What i mean when I say "Use assets swf instead swc" is that SWC is compiled with the app so your final mobile app build would be bulkier if you keep all your assets in SWC file. However if you keep your assets in a SWF file, you can load that at runtime (whenever and/or if required). This way your mobile app build would be lighter (thus less data transferred during installation on mobile device) and load time could also be quicker.
DeleteHope I cleared your query.
So many great tips! Your striped is so on point!
ReplyDeleteSirius performance app
The fundamental consideration with delivering business applications over mobile phones is the huge number of devices, and the wide variety of features on these. digital scales app
ReplyDeleteWow, cool post. I'd like to write like this too - taking time and real hard work to make a great article... but I put things off too much and never seem to get started. Thanks though. UFS Socket for EasyJtagPlus Box
ReplyDelete