Kapta · 15/09/2026
Plan languages by task and content, including who reviews translations. Translating menus is not enough for a municipal app: notices, contacts, error messages and updates also need to be understandable.
Which languages should come first?
Use service enquiries and observed audiences to set priorities. Portuguese and English can be an initial hypothesis to test in an Algarve project, but the decision should fit the operation. Do not confuse a phone's configured language with a preference the user has selected.
How can translations stay aligned?
Link language versions to the same content and record when a translation becomes outdated. Define who reviews sensitive information before publication. Users should be able to identify the date and source of the text they are reading.
What if a translation is not yet available?
Choose an explicit behaviour: identify the available language, provide access to the authoritative version and direct people to suitable official information. Do not automatically present older text as the translation of a new notice.
How should the visitor experience be tested?
Ask people unfamiliar with the municipality to find a contact and interpret information validity. Observe place names and language changes during a journey. Kapta can include these checks when designing an app for residents and visitors.
Next step
Explore Kapta institutional services (Portuguese) and describe your project.
