I am an Android developer and enthusiast with over 10 years of Java development experience. I'm big fan of good design an appreciate well though usability design in applications. Juhani is a DZone MVB and is not an employee of DZone and has posted 111 posts at DZone. You can read more from them at their website. View Full User Profile

Common Mistakes when Porting iOS apps to Android

  • submit to reddit
In the last 6 months we have seen a flood of apps that have gained reputation on iOS being brought over to Android. Unfortunately many of these apps have been design disasters. Almost all of these apps fall into the same trap: not learning the target platform before doing the design.

Android is not iOS. The platform works differently. We, as Android users and developers, do not complain about these apps because we don't want Android apps look like iOS apps we complain because they break the platform guidelines and consistency. Android users have learned to use their devices in certain way. Apps that follow the Android design guidelines are easy to use and learn for Android users. Apps that follow iOS guidelines are easy to use on iOS but on on Android.

When the first one of these apps came out, Readability, I wrote a detailed post about it. Although I got a very positive response from the Readability folks who began fixing the problems other app that followed made the same mistakes. I've gathered some of them here and pointing out some of the most common mistakes. This post is not meant to be hostile or finger pointing / laughing at these apps. I sincerely hope that others would learn from these mistakes and reach better results.

Common mistake: Sharing

Android intent system is great for sharing. I've written about it before here and here. Use intents to share!

Turntable.fm, Instagram, Flipboard and 500px all implement sharing wrong.

Common mistake: iOS icons

Android has set of standard icons for common tasks like sharing. Android users know what to look for. Don't use iOS sharing icon in your app!

Turntable.fm and 500px both use iOS icons.

Common mistake: Right caret in lists

Android Design guidelines clearly states that lists should not use right caret.

Turntable.fm and Instagram both break this guideline.

Common mistake: On-screen back button

Fortunately, this is less common nowadays but this is critical. Android apps should not have an on-screen back button. Instagram fails in this.

The list goes on, Android UI Anti-Patterns on G+

Unfortunately, these apps here are just few of the bad examples we have seen lately and this list isn't complete.

+Paul Burke started a Google+ page for Android UI Anti-Patterns where we plan to keep eye on emerging anti-patterns on Android. The page is not meant to be a place where apps are mocked and laughed at but a page to teach and learn from mistakes made by others. The page will also be only limited to apps that have a large team behind them. Individual developers should never be used as bad examples.

PS. Thanks to Paul Burke for sending me the Turntable.fm screenshots!
Published at DZone with permission of Juhani Lehtimaki, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)


Herry Johnson replied on Tue, 2012/06/12 - 2:05pm

Thanks ejp but initially if the combo box is not empty. that means if he did not typed any letter i will be displaying all the names. My problem is if there are 5000 customers then what? will it not create a performance issue.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.