The following points can be used as the techniques that need to
be avoided in order to avoid any kind of system failure in the Android
software development. If you come to know that the any of the following
has been used by any of your apps then you must patch it up immediately.
Avoid the use of Internal APIs
Though there has been a strong notice to the users against using such a technique but still many of the developers make use of the Internal APIs. The most commonly used technique are the Bluetooth toggle APIs and internal brightness control APIs which was there in the 1.0 and 1.1 versions. There was also a bug that gave the apps free usage of the API even without any prior permission which was later fixed in the Android 1.5. As a result of this it was found out that the apps in the Android 1.5 which made use of the APIs broke down. So it is necessary to find out if your apps are using any of the APIs and if so it's better to update the Android apps.
Avoid direct manipulation of settings
Though using this technique is not strictly prohibited due to the reason that there were some changes made in the behaviour in the Android software development, The main reason for bringing about such changes was due to the activities of certain outsource Android development and the concerned developers. Without even informing the users many of the apps were automatically changing the settings of the system. But now the settings cannot be manipulated by the apps without prior permission. In order to open the configuration settings screen the apps will now have to send intent and only then they can make the necessary changes manually. Under the Android.provider.Settings.Secure class only those settings that are affected have been moved to the Settings Secure class.
Avoid the technique of overboard with layouts
The view rendering infrastructure has undergone changes as a result of which the layout of the view hierarchies can lead to system crashes, However the Android software development 1.5 has been able to expose this problem much ahead than the Android 1.1. The layout can be simplified using the Frame Layout and Table Layout.
Avoid assuming bad hardware
Soft keyboards are supported by Android 1.5 and very soon the physical keyboards will wipe off completely. In case of the physical keyboards assumption by your Android apps development then it becomes imperative to make it degrade and assume only the soft keyboard as early as possible.
Avoid the technique of rotations ash are not cautious
All the devise that are on the Android 1.5 or later versions will have the capability to rotate the screen based on the user's orientation with the device. In certain 1.5 Android devices this will be done automatically by the system but many others the user can enable the option. As a result of this the Android apps development will start performing unexpected activities due to the re-orientations by their own. This happens under the assumption that the rotation of the screen is possible only if the physical keyboard has been exposed. In the absence of physical keyboard such re-orientation will never take place.
Avoid the use of Internal APIs
Though there has been a strong notice to the users against using such a technique but still many of the developers make use of the Internal APIs. The most commonly used technique are the Bluetooth toggle APIs and internal brightness control APIs which was there in the 1.0 and 1.1 versions. There was also a bug that gave the apps free usage of the API even without any prior permission which was later fixed in the Android 1.5. As a result of this it was found out that the apps in the Android 1.5 which made use of the APIs broke down. So it is necessary to find out if your apps are using any of the APIs and if so it's better to update the Android apps.
Avoid direct manipulation of settings
Though using this technique is not strictly prohibited due to the reason that there were some changes made in the behaviour in the Android software development, The main reason for bringing about such changes was due to the activities of certain outsource Android development and the concerned developers. Without even informing the users many of the apps were automatically changing the settings of the system. But now the settings cannot be manipulated by the apps without prior permission. In order to open the configuration settings screen the apps will now have to send intent and only then they can make the necessary changes manually. Under the Android.provider.Settings.Secure class only those settings that are affected have been moved to the Settings Secure class.
Avoid the technique of overboard with layouts
The view rendering infrastructure has undergone changes as a result of which the layout of the view hierarchies can lead to system crashes, However the Android software development 1.5 has been able to expose this problem much ahead than the Android 1.1. The layout can be simplified using the Frame Layout and Table Layout.
Avoid assuming bad hardware
Soft keyboards are supported by Android 1.5 and very soon the physical keyboards will wipe off completely. In case of the physical keyboards assumption by your Android apps development then it becomes imperative to make it degrade and assume only the soft keyboard as early as possible.
Avoid the technique of rotations ash are not cautious
All the devise that are on the Android 1.5 or later versions will have the capability to rotate the screen based on the user's orientation with the device. In certain 1.5 Android devices this will be done automatically by the system but many others the user can enable the option. As a result of this the Android apps development will start performing unexpected activities due to the re-orientations by their own. This happens under the assumption that the rotation of the screen is possible only if the physical keyboard has been exposed. In the absence of physical keyboard such re-orientation will never take place.
For More Info:- Android Software Development
[http://www.mobi-people.com/android-development.html] | Android Apps
[http://www.mobi-people.com/android-development.html]
Article Source:
http://EzineArticles.com/?expert=Daniel_Will
No comments:
Post a Comment