I can see where he's coming from, my company is actually at fault on this exact point.
The initial target was iOS and then clients requested Android compatibility as well. Designs for iOS are completed and implemented and are then re-used for Android. The excuse is 'consistent user experience' but really they just don't want to do the same job twice for a platform that generally has less usage and provides less profit (in our case at least).
I took matters into my own hands and there are noticeable differences between the two applications. There was of course some backlash (I flat out refused to put a 'back' button on the action bar for example or move the sliding menu to the right side) but in general the look and feel is consistent across the two platforms.
That doesn't (and won't) stop me from using native controls such as text inputs and dialogs that users on Android are quite familiar with.
In case someone has no clue what the hell I'm talking about I'd be happy to share some screenshots via pm.
The initial target was iOS and then clients requested Android compatibility as well. Designs for iOS are completed and implemented and are then re-used for Android. The excuse is 'consistent user experience' but really they just don't want to do the same job twice for a platform that generally has less usage and provides less profit (in our case at least).
I took matters into my own hands and there are noticeable differences between the two applications. There was of course some backlash (I flat out refused to put a 'back' button on the action bar for example or move the sliding menu to the right side) but in general the look and feel is consistent across the two platforms.
That doesn't (and won't) stop me from using native controls such as text inputs and dialogs that users on Android are quite familiar with.
In case someone has no clue what the hell I'm talking about I'd be happy to share some screenshots via pm.