5 Mistakes That Android Developer Makes in Their Apps


Android apps are ever growing and there seems to be no stopping for the android app development industries. With growing competition, the developers need to be more wary while developing the apps. At the core, developing an android app is a tricky job. Even best of the developers might make a few mistakes. However, how would we learn without making mistakes? We list five mistakes that android developers would make!

1) Blocking requests that are found on UI-threads

You might have come across experiences like applications hanging and ceasing to respond to the inputs. The animations might have stopped sparkling, or there maybe any emergencies that could happen. This is due to blocking of UI-thread of your application. This is a grave sin if you need to make sure of smooth performance of the app. Use Thread pool executors and Async Tasks to put your blocking calls on worker threads. When the background task is completed you could post messages or use callbacks to UI-thread’s message loop in order to process the results.

2) Too many large images

It is hard to handle huge bitmap images on Android. We haven’t yet come across anything which would help in loading as much images as we like without falling short of memory. The main reason is that the quantity of RAM that is available on Android applications for individual processes is small. You would observe that loading of few images into the memory could result in your application drying out of heap space rapidly. You could try making use of Android Large ahead attribute that is in application manifest; in order to request larger heap space. You could also get rid of the images off the heap very soon. Ensure recycling of bitmaps is made once you’re done. Do not load those images which would be bigger than the screen.

3) Absence of visual feedback while touching buttons

This is a really simple problem that could be solved but is poorly done. The application is supposed to react positively when users choose to interact with display of the application. The touch button must be highlighted. It is really easy to offer various graphic states to the on screen elements depending on the pressed states or current selection. You need to custom your screen elements and it could be easily done by creating a drawable XML file using a state selector. You must be prudent about where to place these sorts of drawables. There wouldn’t be any need of it on button objects which are regular. You wouldn’t even have to use it on single ListViews rows.

4) Android apps which appear like iOS apps

Many people wish to port prevailing iOS apps onto the platform of Android and wish to recycle that same design. It could be a horrible thing to break. Android applications contain their own feel and look which is different from iOS or any other platform for that matter. Android users are often seen providing poor review and ratings to those applications of android that manage to look like those of iOS. Google has got a Design Guidelines that is extensive and explains how applications on Android must appear. Go through them!

5) Lack of support for formats of multiple devices

The fragmentation of android devices is real. There are various versions of operating systems; various screen sizes and plenty of keyboard layouts. A lot of applications poorly support such diverse devices of Android. It needn’t really be that hard. Android offers developers plenty of tools to fight this problem. Use density independent pixels to layout the UI. Make use of XML resources to layout screens. Alternate layouts could be provided for various screen sizes.


Hope you found this article to be useful. Let us know what you think via the comments.

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>