Enhancing Global UX: Automatic Location-Based Translation vs. Manual Language Selection

[ild0tt0re]

I wanted to share some thoughts on why using automatic translation based on the user’s location is a game changer for our web app.

When the app detects a user’s location, it can instantly display the interface and all related resources (including JW content) in their native language. This seamless, localized experience means users don’t have to go through the extra step of manually selecting the right language starting from English first content. It simplifies the user journey, minimizes friction, and immediately creates a more welcoming, intuitive experience.

Overall, this approach streamlines usability and makes the app feel more personalized and user-friendly from the moment they land on it.

Would love to hear your thoughts on this.

[ux-git]

I guess @rhahao is already discovering or implementing the browser language detection and therefore displaying user's language upon first load. Compared to using location detection, this won't require any location permissions prompting. @rhahao what do you think?

[rhahao]

Sure. For now, we will go with the approach of getting the browser language. I hope to have it tested asap. Thanks.

[ux-git]

@rhahao what do you think about linking the Meeting materials language with the selected UI language during the Initial congregation setup?

This way in most cases the correct language will be pre-selected and it will cause less issues even if the initial setup has been quickly and "carelessly" tuned.

Or... does Organized already do this? 😄

[rhahao]

Great idea! Not yet available, but I’ll add it. 😁

[rhahao]

#3722 This specific one will be included in the next app release.

[ux-git]

Great idea! Not yet available, but I’ll add it. 😁

Many thanks to @ild0tt0re for discovering this potential for improvement

[rhahao]

@ild0tt0re, @ux-git: FYI, implemented in #4040