Over a million developers have joined DZone.

Localized or Locale? Building and Testing a Localized Application for Windows Phone

DZone's Guide to

Localized or Locale? Building and Testing a Localized Application for Windows Phone

· Mobile Zone
Free Resource

Discover how to focus on operators for Reactive Programming and how they are essential to react to data in your application.  Brought to you in partnership with Wakanda

It’s been about three weeks now, that my first application “MyDiary” has been published on Marketplace and I am quite thrilled that there are some downloads. It’s not going to make me rich, but that was never the goal anyway. I am just happy to see that I created something that people seem to like.

When I saw the downloads, and the market those downloads came from, I started thinking. So far, my application was just supporting English. But the German market seems to be interested in “MyDiary”. Being German myself, I know that only roughly 60% of the German population speak English. That was the reason to think about a localized or a local version of “MyDiary”.

Frankly, I don’t really know much (yet) about localized applications, but here you can find some information about how to build and test a localized application for Windows Phone.

I went for a different approach though. I just created a German version of “MyDiary”, called “Tagebuch” and submitted it not only to the German market, but to all markets. The advantage in my opinion is, that the German application name now could attract more users.

Basically I had to create the whole thing from scratch again and along with some German texts of course do some minor changes inside the code. For example, “MyDiary” stores diary entries together with the location where you created and the date when you created those entries. By default the date is being displayed like this:


In a German version I want the date being displayed in German, so obviously I have to add something in my MainPage’s constructor:

Thread.CurrentThread.CurrentCulture = new CultureInfo("de-DE");

The date now looks like this:


Take a look at this to learn more about Culture Info.

My applications don’t support multiple languages, but at the same time users choose the language they want in the moment they download the application. I deliberately chose this approach, because I wanted users to be able to use the language they want to, independent from where they download the app. If they live in the USA they can choose to download the German version or the English version. Like I live in the Netherlands, but I like to have my applications in English.

Oh, and while I was at it, I also created a Dutch version, called “Dagboek” that is ready to submit. While I basically developed only one app, with the German and the Dutch version, I will have three applications on Marketplace.

If you are interested in German versions as well, and you have questions about translations, don’t hesitate to contact me either on this blog via a comment or via Twitter @andidrea.


To be continued…

Learn how divergent branches can appear in your repository and how to better understand why they are called “branches".  Brought to you in partnership with Wakanda


Published at DZone with permission of Andrea Haubner, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

The best of DZone straight to your inbox.

Please provide a valid email address.

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}