All have been exclusively iOS users, with no feel for how the two platforms differ, and I have had to take it up on my self to translate and adjust the designs given to me so that they follow norms and practices on Android.
Generally, the further a design strays from native UI elements the more difficult it's going to be to implement in a way that covers edge cases well and is accessibility-friendly. Sure I can bodge something that looks like the mockup but it's not going to feel half as nice to use in practice because it required me to write a lot more bespoke widget code, and there are considerations that went into the stock widgets that the designer probably isn't taking into account.
In these situations a little bit of leeway to bend designs to be closer to the OS baseline help quite a lot (e.g. do you really need that custom typeface which isn't built for use in UIs? Probably not), and so I greatly value designers who have the skill to build around what's already there instead of trying to replace it outright. That kind of design work isn't as sexy but it's far more practical.
It appears to me that they also do not differentiate between screens and modals and just pick at random which flow will be which. I am not faulting them for that, as Apple has gone pretty wild with modals lately too, but still, at least some consistency would be nice.
- "Just do the same as iOS" when asking about Android
- Hardcoded assumptions about layout size (less an issue now since iOS is more fragmented than before)
- Not handing edge cases, especially long string lengths
- Way overusing opacity (or blur before apple gave tools for it) which tanked performance for an absolutely minimal visual flourish
- Terrible tap targets
See if you can get your designers/developers to install Google's Accessibility Scanner[0]. It brings tap targets and accessibility to the front of their minds when working.
[0] https://play.google.com/store/apps/details?id=com.google.and...