Custom Language Translation

[jgarcia_qk4]

The new Instant App Language Switcher in ArcGIS Online is a great feature. After selecting a language, the "translation configuration" dialog box lets you fine-tune the wording to better match your needs.

However, many smaller languages, such as many Native American languages, are not available as selectable options. To support these cases, users should be able to configure a custom translation option in the "translation configuration" dialog box. This would allow them to define their own language label and translations, making the app more inclusive for communities whose languages are not currently listed.

[BethRomero]

@jgarcia_qk4 thanks for your idea. What language are you looking to have added to the partial support list? While we explore the options for this idea, we may be able to add the requested language for a future release. 

[jgarcia_qk4]

@BethRomero The language I wanted to incorporate into my project which inspired this idea is Western Apache. As is the case with many indigenous languages, a direct translation for all components of an Instant App would not be possible.
It would be good practice for an Instant App author (if they do not speak the language) to consult with a fluent speaker for each component of each app they make to ensure a translation allows users to navigate the tool, which may require small tweaks depending on context or regional dialect. This idea is as much about increasing tribal sovereignty and promoting language preservation as it is accessibility. 

[BethRomero]

@jgarcia_qk4 The language switcher supports two types of languages: full and partially supported languages. Partially supported language allows for the translation of app-authored text only. This is done by entering translated text for any app-authorized text. We can't translate components and other Esri-defined text, which is only supported for languages that ArcGIS Online supports. This blog article provides a more detailed explanation of the differences between partial and full support. We could add Western Apache (apw) to the list of partially supported languages in the next update of ArcGIS Online.

[jgarcia_qk4]

@BethRomero Thank you for that clarification -- the inclusion of Western Apache and even just a handful of the more commonly spoken North American indigenous languages to the partially supported group would be a great addition to this feature.

Ideally, any language with an ISO 639-3 code would be available as partially supported, since users can enter the translations for app-authored text themselves. It would open the door for a lot of smaller indigenous languages who may not have many speakers but are trying to promote and incorporate their traditional language across the board.

[BethRomero]

@jgarcia_qk4 Western Apache has been added as a partially supported language; it was included in the October 2025 update. 

[jgarcia_qk4]

@BethRomero @IanWittenmyer 
I am very happy to see Western Apache be added to AGOL for Instant Apps and I appreciate ESRI paying attention to this concern --- however this suggestion should not be marked as "implemented". My suggestion was not to add a particular language for the project I personally was working on at the time, but to provide a framework to add other indigenous languages. Any language with an ISO 639-3 code should at least be able to be selected as "partially supported" since it relies fully on the end-user to provide the translation. Partially-supported language translation is one of the most exciting features in AGOL right now, I hope to see its functionality expanded!