Language Selector #35

Closed
opened 2025-02-25 18:20:39 -08:00 by Vutukuri15 · 1 comment
Vutukuri15 commented 2025-02-25 18:20:39 -08:00 (Migrated from github.com)

User Story

As a poker game host,
I want to change the application language to my preferred language (e.g., English, Spanish, French, etc.),
So that I can easily understand and navigate the app in my preferred language.

Acceptance Criteria

  • A language selection option is available in the app settings.
  • The app supports at least English and other commonly desired languages.
  • Once a language is selected, all text elements in the app (buttons, labels, instructions) update accordingly.
  • The default language is English, unless changed by the user.
### User Story As a poker game host, I want to change the application language to my preferred language (e.g., English, Spanish, French, etc.), So that I can easily understand and navigate the app in my preferred language. ### Acceptance Criteria * A language selection option is available in the app settings. * The app supports at least English and other commonly desired languages. * Once a language is selected, all text elements in the app (buttons, labels, instructions) update accordingly. * The default language is English, unless changed by the user.
djwesty commented 2025-02-26 20:29:49 -08:00 (Migrated from github.com)

I've worked on mobile apps which support multi-language, so here are a few thoughts

  • Often the app will try to default to the language which matches the phone OS language, and pick English as a fallback if our app does not have that support. If that is non-trivial, simply defaulting to English is fine too
  • There is probably a best supported approach for multi-language on expo (or atleast more generally for react native). That should be where to start.
  • At minimum, we can just support one additional language. This could be whatever language the implementer decides. I would personally choose Spanish since I am somewhat familiar, but it can be anything.
  • Our app does not really have a "Settings" feature, so I would say adding a drop-down selector to the title bar would be a decent approach, but this is flexible
  • It will probably be necessary to touch most of the source files, and possibly fix up existing tests. In my opinion, maybe adding one high level for the 2nd language makes sense, but I usually do not test alternate languages across the units of the entire app
I've worked on mobile apps which support multi-language, so here are a few thoughts - Often the app will try to default to the language which matches the phone OS language, and pick English as a fallback if our app does not have that support. If that is non-trivial, simply defaulting to English is fine too - There is probably a best supported approach for multi-language on expo (or atleast more generally for react native). That should be where to start. - At minimum, we can just support one additional language. This could be whatever language the implementer decides. I would personally choose Spanish since I am somewhat familiar, but it can be anything. - Our app does not really have a "Settings" feature, so I would say adding a drop-down selector to the title bar would be a decent approach, but this is flexible - It will probably be necessary to touch most of the source files, and possibly fix up existing tests. In my opinion, maybe adding one high level for the 2nd language makes sense, but I usually do not test alternate languages across the units of the entire app
Sign in to join this conversation.
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: david/poker-chips-helper#35
No description provided.