Summary
We kicked off this chapter with an introduction to localization, understanding its importance in ensuring our app resonates with users globally. Before diving deep, we explored the basics of how localizable values can be statically bound, offering a foundational approach.
Building on this, we introduced a more dynamic localization framework. This allowed for more flexible updates and interactions. Following this, we delved into simplifying our XAML through the Translate markup extension. While it made our data-binding statements sleeker, the underlying mechanism remained unchanged.
Next, we discussed getting localized data from our APIs. We found a neat way to tell the API about the user’s language choice without making our code messy. By using the ILocalizationManager, we kept our approach consistent. And, with Messaging, our app knows when to fetch new data if a user changes their language.
The big takeaway? All our steps respected the key MVVM idea of “...
