SyndicationFeb212012
02:27:48 pm
02:27:48 pm
Building A Mobile App Using Flash Builder 4.5
Flash Builder categorises each device as having one of three screen densities, either 160, 240 or 320 dpi.
Bitmap images however shrink and grow very poorly and so the above method is not suitable. To handle that, Adobe have provided your "MultiDpiBitmapSource". This is where should you use a bitmap as the icon for a button, you can provide 3 different versions in the same bitmap to that button, each sized to target screen density 160, 240 and also 320. Flash Builder will detect what the device is and use a appropriate bitmap as that icon.
Finally you can also provide different settings in your css file that help you change settings for several screen densities, and also different Operating system.
The result is which you could code once and then and after spending some effort making certain it looks as good as possible in various situations, it will look not bad in most devices. If you are targeting full spectrum of devices you have got to have some sort of trade-off of time spent on styling v the payback for any device. Some research into the audience size for any device and then prioritization will help you to make appropriate decisions on which the main device ought to be and then how enough time should be spent styling for any other devices.
Testing the App in Whizz Builder
Flash Builder carries a good method of to be able to see what your screen look like on different devices. Firstly at design time you may choose from a drop down list of devices and see the final results. Then by choosing different run configurations by Main system and device, you can run the applying and see the results on each device.
Other than styling issues there didn't seem to be any differences in that this App behaved on each device with regard to runtime errors.
Testing Your App for a Device
After getting developed and styled ones App using Flash Builder you will probably want to test it on that machines themselves prior to deploying it to your market place. The simulator within Flash Builder provides reasonable approximation of that this App will look on each device but it's totally different from using it on this device.
There are a multitude of smart phones available so rather then buying each individual unit and testing it with each, you will probably prefer to test on one of each one of the three operating systems which might be Android, iOS (iphone4 and iPad) together with QNX (Blackberry Product). With Android devices the approach is quite simple. Essentially you create some sort of dummy certificate using Flash Builder and then you can connect and download your App for your device.
Apple devices are even more difficult to test on. You have to apply to Apple to get a developer licence which gives you a developer key, then get a key for your device and use a two keys to set up it to iTunes and then use iTunes to set it up on your device.
The Blackberry Playbook is still quite new and has not had demonstrably rave reviews so the quantity of your users that can actually install your App for a Blackberry Playbook is probably now quite small. http://onetimeconstruction.net/
Bitmap images however shrink and grow very poorly and so the above method is not suitable. To handle that, Adobe have provided your "MultiDpiBitmapSource". This is where should you use a bitmap as the icon for a button, you can provide 3 different versions in the same bitmap to that button, each sized to target screen density 160, 240 and also 320. Flash Builder will detect what the device is and use a appropriate bitmap as that icon.
Finally you can also provide different settings in your css file that help you change settings for several screen densities, and also different Operating system.
The result is which you could code once and then and after spending some effort making certain it looks as good as possible in various situations, it will look not bad in most devices. If you are targeting full spectrum of devices you have got to have some sort of trade-off of time spent on styling v the payback for any device. Some research into the audience size for any device and then prioritization will help you to make appropriate decisions on which the main device ought to be and then how enough time should be spent styling for any other devices.
Testing the App in Whizz Builder
Flash Builder carries a good method of to be able to see what your screen look like on different devices. Firstly at design time you may choose from a drop down list of devices and see the final results. Then by choosing different run configurations by Main system and device, you can run the applying and see the results on each device.
Other than styling issues there didn't seem to be any differences in that this App behaved on each device with regard to runtime errors.
Testing Your App for a Device
After getting developed and styled ones App using Flash Builder you will probably want to test it on that machines themselves prior to deploying it to your market place. The simulator within Flash Builder provides reasonable approximation of that this App will look on each device but it's totally different from using it on this device.
There are a multitude of smart phones available so rather then buying each individual unit and testing it with each, you will probably prefer to test on one of each one of the three operating systems which might be Android, iOS (iphone4 and iPad) together with QNX (Blackberry Product). With Android devices the approach is quite simple. Essentially you create some sort of dummy certificate using Flash Builder and then you can connect and download your App for your device.
Apple devices are even more difficult to test on. You have to apply to Apple to get a developer licence which gives you a developer key, then get a key for your device and use a two keys to set up it to iTunes and then use iTunes to set it up on your device.
The Blackberry Playbook is still quite new and has not had demonstrably rave reviews so the quantity of your users that can actually install your App for a Blackberry Playbook is probably now quite small. http://onetimeconstruction.net/
No Comment for this post yet...