It is very important that you future proof your applications so that you can weather the quick change of platforms for different users. There are a few things that you should avoid when you create the apps in order for you to do great apps that will last the test of time.
Avoid Using Internal APIs
There are some developers who still use unsupported or internal APIs. For example, these apps make use of internal brightness control as well as Bluetooth switch APIs that were highly used in 1.0 and 1.1. However, in Android 1.5, this bug was fixed. With this, apps that previously used APIs crashed and burned when run on Android 1.5. If you have created applications that run internal APIs, you need to update them as soon as possible so that they can still be usable with the new platform. Make the necessary changes now.
Avoid Manipulating Settings Directly
Initially, this would not really be a problem however this was caused by a change in behaviour that Android has innately. There are other apps from other developers that are trying to change the settings of the system without even providing adequate notice for the user. Because of this, other apps cannot directly manipulate the values of the other aspects under settings. The apps won’t really crash but the apps can be classified as too slow to function properly or may not really function at all.
Avoid Overdoing the Layouts
There have been a lot of changes done on View rendering infrastructure which is quite difficult to count now and the changes have been quite broad in nature too. With these, crashes are highly possible and this can be detrimental to the apps you are creating. Complex layouts for your apps can be a big problem but Android 1.5 readily shows you the problem compared to having the Android 1.1 before. The best thing to do is to simplify the layouts. Try to utilize FrameLayout or TableLayout for this.
Avoid Having Negative Hardware Assumptions
Android 1.5 initially started with soft keyboard enabled apps but in the future, there will be more gadgets that will eliminate this feature and then just have touch keyboards. If your app needs the use of physical keyboards then when you make changes on it, do it so slowly so as to adapt to the gradual changes in devices as well.
This article was written by the sell mobile phone price comparison website, sellmymobile.com. The site helps visitors in the recycling of their old, new or broken mobile phones , by providing a comparison of what the leading UK recyclers offer for their mobile phone.