An Android language preferences brief defines which languages an app supports, how people choose between them and what happens to content that has not been translated. A language menu is only one part of that work. The business also needs approved terminology, a clear fallback and a test process for complete user journeys.
For a company commissioning Android app development in Kenya, this worksheet connects translation decisions to the actual app experience. Examples are illustrative requirements, not claims that a particular Mocky app supports any named language. Language support, scope and ongoing maintenance should be agreed for the specific project.
Identify the tasks and languages that matter
Start with the people who will use the app and the tasks they need to complete. Avoid selecting languages only because a competitor lists them. Explain where a language helps someone understand instructions, enter information or review a consequential decision.
Choose a first release scope the business can maintain. A complete, reviewed translation for essential journeys can be more useful than many selectable languages containing mostly untranslated screens. The product owner should decide which languages are ready to advertise and which remain under preparation.
Record the distinction between interface text and business content. Navigation labels may be translated while a customer-entered note remains in its original language. An item supplied by another service may follow separate rules. Make those boundaries visible in the brief so the language selector does not imply that every record will be translated automatically.
Define where the language preference belongs
Decide whether the preference follows the device, the signed-in account or both. Someone using two phones may expect the same account language everywhere, while a shared device may require a different arrangement. Document the intended result instead of assuming that a stored setting has an obvious owner.
Android's per-app language documentation describes system-level language preferences introduced in Android 13 and APIs for supporting app-specific choices. Ask the implementation team to explain the behaviour on the project's supported Android versions, including any in-app selector and its relationship to system settings.
Avoid presenting the app setting as though it changes the entire phone language. The interface should explain what the choice affects. If an account preference also controls messages generated by a server, describe that separate relationship and confirm how the services keep the selected value consistent.
Build a translation register with context
Give each interface message a stable reference and enough context for a translator to understand its purpose. A short word such as open can describe a status, an action or a business hour. The translator needs the intended meaning rather than a spreadsheet full of isolated words.
Include headings, buttons, errors, confirmation text, empty states and permission explanations. Translating only the main dashboard can leave the difficult recovery journeys in another language. Capture any text coming from external services and identify which team can actually change it.
Use approved terminology for recurring business concepts. A task, request and order should not become interchangeable merely because different screens were translated separately. Keep a small glossary with a responsible reviewer, and show related messages together when approving a term that appears across several workflows.
Choose fallbacks deliberately
Define what happens when a selected language lacks a particular translation. The app should have an agreed fallback rather than showing an internal message identifier or an empty control. Ask the developer to demonstrate that behaviour using a controlled missing translation during acceptance.
Distinguish missing interface translation from content that is intentionally preserved. A customer name, document title or entered description may need to remain exactly as supplied. Do not automatically translate identifiers or operational text that must retain its original meaning for staff to recognise the record.
If external content is available only in one language, decide how to explain the boundary before the person opens it. A translated menu should not suggest that an attached document or third-party help page is also translated. Make the actual experience understandable without promising capabilities outside the project's control.
Preserve work when the preference changes
A person may switch languages while entering a report or reviewing a form. Specify whether the app preserves unsaved values, returns to the same screen and updates labels immediately or through another clear step. The accepted behaviour should not silently discard work.
Ask the team to test a change during a waiting request and after reopening the app. The selected language should remain understandable across those transitions. A translated success message should still refer to the same action and record, rather than an unrelated screen reached after a restart.
For shared hardware, coordinate with the Android shared devices brief. Decide what happens at sign-out and account change. One operator's language preference should not expose their records or make another operator appear to approve a decision under the wrong account.
Keep language separate from dates and amounts
Changing interface language can interact with formatting, but it should not silently change the business meaning of stored values. A date-only appointment field and a timestamp represent different information. Labels, parsing and display need to remain consistent with the underlying requirements.
Review the Android dates and times brief for that distinction. Add examples where the same approved record is viewed under each supported language. The displayed explanation may change while the actual appointment or recorded event remains the same.
Also test quantities, currency labels and decimal input where relevant. Ask the implementation team to show the supported formats and correction messages. Do not prescribe unverified financial or locale rules from a translated screenshot. The business should approve the intended interpretation and the trusted system should validate submitted values.
Review complete screens with realistic text
Translations can occupy different amounts of space. Use the actual approved wording in review, including long buttons, multi-line labels and validation messages. A screen that works with short placeholder text may clip the meaning of a consequential action after translation.
Test the supported phone sizes and system text settings. Keep the Android text size acceptance brief as the broader layout matrix. Language testing adds real translated content and meaning checks, rather than replacing the existing readability evaluation.
Ask a fluent reviewer to complete a realistic task in the selected language and explain the outcome. Literal word accuracy alone is insufficient if the person misunderstands whether a request is pending or complete. Review related message pairs, such as confirm and cancel, together with the surrounding explanation.
Assign ownership for future changes
Every new feature can introduce text that needs translation and review. Agree who prepares source wording, who translates, who approves and what prevents an incomplete language from being presented as fully supported. Keep those responsibilities in the release process rather than relying on a developer to remember them informally.
Maintain versioned translation records with suitable context and approval status. If the business changes the meaning of a workflow, review the translated messages too. A small source-language edit can create a substantive contradiction if older translations retain the previous instruction.
Use controlled data for acceptance and avoid sending live customer messages simply to preview another language. Verify the generated copy through isolated destinations or blocked delivery. The project should demonstrate the experience without creating fictional business activity or exposing private records to reviewers.
Before requesting an Android app quotation, provide the language list, task coverage, content boundaries, fallback rules and review owners. Mocky's app portfolio provides available examples of app work, while your supported languages and acceptance evidence remain specific to the commissioned project. Clear ownership makes the proposed feature reviewable without promising effortless translation or guaranteed adoption.
Frequently asked questions
Does a language selector translate customer-entered text?
Not automatically. Define interface translation, business content and external documents separately, and explain their actual coverage.
Should the setting follow the account or phone?
Choose the behaviour around the users and devices involved. Document shared-device and multi-device scenarios before implementation.
Can we launch with partly translated screens?
Agree an honest release scope and fallback. Do not advertise complete support when essential journeys are still unavailable in that language.
Who approves translated business terminology?
Assign a fluent reviewer with the relevant business context. Developers can implement approved text, but should not invent its operational meaning.