[aferreira]

One thing that I like about Android is that developers can choose to minimally style buttons and similar UI elements and these differences will be applied to whatever the base device theme is.

This means that users will get a consistent user experience throughout various applications and won't have to run around trying to figure out what's a button and what's a text input.

Sadly, this project essentially destroys all of that work and something tells me it won't work correctly on the most customized devices (like the old Motorola RAZR running 2.3 for example).

Nice idea but I don't think it makes much sense in it's current state.

[radley]

Following UX/UI patterns make sense, but not design - especially if you plan to be cross platform.

[thwarted]

What's the logic here? If you're cross platform, most people are most likely not going to be using your app on more than one platform, so there's little to be gained from a "consistent experience across platforms" angle. It's rare that the same person or team is doing both iOS and Android development, and the languages and layout methods are different anyway, so there's little to be gained on the development side in terms of reuse. Maybe it makes sense if you only have one "mobile PM" who handles both, but this seems shortsighted considering how quickly the platforms change and, especially on Android, how many devices and carrier customized builds you need to test on.

I suppose it makes sense from a branding perspective, but any designer worth their weight should be able to come up with a distinctive branded experience that doesn't revamp the entire, default, builtin experience on the device.

[aferreira]

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.

[thwarted]

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

Yeah, this is a sign of a bad PM, who doesn't understand the market or mobile ecosystem enough to realize that the targets are completely different.

On the other hand, if the interface was designed to be completely unique and skirted all the specifics of the deployment platform, in an attempt to be branded or for reuse of designs, that's reasonable. Often, however, it is obvious that the design was optimized for another platform than the one you're using it on. "Custom back button" on Android, indeed.

[dragos2]

I too am faced with the "custom back button" on Android. I just smile and carry on.

[CervezaPorFavor]

I hate it when apps don't feel 'native' for the sake of cross-platform consistency. It's stupid.