I just ran into this on an onboarding flow. In Canada we saw a 9% drop when French speakers got fr-FR defaults (comma decimals and DD/MM/YYYY) instead of fr-CA; switching to separate language and region selection fixed it but added one extra step. How are you handling this — decouple language and region up front, infer region, or correct later without adding friction?
I’ve noticed similar drops too… Decoupling can help, but maybe testing with localized defaults would ease the burden? Ever tried A/B testing on that? ?
Testing your defaults sounds smart — I’ve found that even slight adjustments in locale can impact user trust… @mentioning your A/B tests could clarify if there’s a specific regional preference; any successes you’ve had there?
It’s crucial to cater to both language and region at the start, as you pointed out with the 9% drop. I’ve found clear user instructions can help smooth the extra step from decoupling, though it does take extra time initially. Have you considered user feedback on your onboarding process? @sophia_m92.
?