When designing a mobile application or mobile website, UX people pay special focus on Android and iOS. It’s because, both platforms have combined market share around 94% and both have different appearance and personality. Both the platforms have their own design guidelines.
If a user has to switch from one platform to another, it takes time to unlearn and learn new platform. It’s a bit painful for the user to shift. Therefore, it’s important to customize mobile experience for each platform. Here, I am listing a few reasons to customize the UX for different platforms.
When designing for one platform forget others and focus on the target platform only.
Device Manufacturer brings hardware differences.
Android is highly fragmented in terms of device and manufacture, and manufacturers have access to modify the OS as per their own device specifications. However iOS is manufactured by Apple only, there are no significant hardware differences in iOS.
Most of the Android devices have three buttons at bottom i.e. home key, back button and option menu. On the contrary iOS has only one button home key. This differentiation creates significant usability variations.
Screen size and resolution
Android is more open and diversified than iOS. It’s easy to predict the screen size and resolution of iOS device, but for Android we need to keep in mind different screen size and resolution. To simplify, android guidelines suggest using set of four generalized sizes: small, normal, large and extra large.
|Screen size measured in||Points(pt)||Density Independent Pixels (DP)|
|Most common resolutions||Tablet (iPad)
Handheld (iPhone, iPod)
iPhone5 Retina (2x)
iPhone6 Retina (2x)
iPhone6+ Retina (3x)
Long press in Android will bring a context menu but not in iOS. Users using iOS expect additional functionality through swipes and taps.
Android have two methods of back. “Up” button at upper left of the main action bar and system “Back” button at bottom left on the physical devices.
iOS back button is software controlled only. It is displayed on the upper left of the main navigation bar. However it is not used to navigate backwards across the device and not all the iOS apps has back button.
Apple made a gesture where user can swipe from left to right and go back in the same app.
Tabs placement – Action buttons
iOS primary tab navigation doesn’t look like tabs. They are icon with placement at bottom of the window. As per iOS guidelines, not more than 5 tabs should be displayed at a time. If tabs are more then 5, “three dots” more icon should be displayed.
Android users expect action buttons (tabs) at the top which user can scroll left or right. Android focus on simplicity and do not use icons for tabs. Android uses text for tabs with border bottom on selected tab.
Android users expect tabs at top and iOS user expect tabs at bottom of the window
Option menu for actions
Android uses UI element spinner for the option menu, which is generally placed at top left of the action bar. iOS uses action sheet which is placed at bottom of the screen.
Search icon in textbox
iOS place search bar at top of the screen and search icon is placed in the center of the texbox. It moves left when user taps on it.
Similar to iOS, Android places the search bar at top of the screen. However the bar is hidden until user tap on the search icon.
Some UI differences
iOS use three horizontal dots with text written more below it and android use 3 vertical dots.
Dropdown – a list of predefined options
A component that displays list of of elements is called spinner in Android and iOS call it picker.
In iOS current page is written in the center and previous page is written at left with back arrow. In Android only current page is written with back icon.
In iOS arrow is placed at right and in Android no arrow is placed.
Android focus more on the branding and place the logo in almost all the pages but iOS mostly place logo in the home page only. But it’s not a defined standard.
Users of different platforms expect different widgets in a certain way. If an app does not behave in expected manners, user will feel alienated on experiencing sudden change in the feature. It’s safer to follow the conventions rather imposing conventions of different platforms. However in some particular circumstances, slight deviation from the standards may help users. In that situation it’s good to put users first.