We’ve been trying to standardize passcode rules across our devices, but it’s still a bit messy. Most of our iOS users are on simple PINs, while Android users keep getting pushed into stricter requirements. Feels kind of inconsistent from their side.
How are you all handling passcode consistency across Android and iOS?Solved
Replies (5)
Yeah, that’s pretty common. Both platforms have their own idea of what “secure” means. If you don’t align it manually, Android usually ends up being more aggressive with the rules.
That’s exactly what we noticed. We stopped overthinking it and just picked a baseline for both. Went with a 6-digit numeric passcode. Once we mapped it properly in the policy, things started feeling a lot more uniform.
Same approach here. The important bit was how we handled Android. We had to explicitly set it to numeric with a minimum length. If not, it quietly starts nudging users toward alphanumeric passwords.
Makes sense. Were there any complaints from users though? Ours already feel passcodes slow them down a bit.
A few at first, yeah. But we kept biometrics fully enabled on both platforms. So the passcode is just there as a backup, and most of the time they’re just using fingerprint or face unlock. After that, no one really noticed the difference.