When developing mobile applications for multiple platforms it can be important to understand how to implement time zones conversion in elegant manner.

Xamarin Forms is a cross-platform natively backed UI toolkit abstraction that allows us to easily create user interfaces that can be shared across Android, iOS, and Windows Phone. It’s implementation of XAML allows us to define user interfaces using markup rather than code, and it is well suited for use with the MVVM (Model-View-ViewModel) application architecture.

First thought on time zone conversions would be to use .NET native TimeZoneInfo class. Since key component of building cross-platform applications is being able to share code across various platform-specific projects, most of the code should be written in Shared projects, Portable Class Libraries (PCLs) or in .NET Standard Libraries (more info). PCL projects target specific profiles that support a known set of .NET Base Class Library (BCL) classes/features for targeting platforms.  .NET Standard is similar to PCL, but with a simpler model for platform support and a greater number of classes from the BCL.

All this implies that only limited set of .NET features is available for PCLs. This is true for TimeZoneInfo class as well, where most of the methods are not available for PCL (including FindSystemTimeZoneById). As nicely explained on Stackoverflow:

This is all entirely by design. Timezone conversions requires an operating system with a database that keeps track of the timezone rules across the world. Available on a desktop class machine, not available on limited devices like a phone. Without the database, you can only know something about UTC and the timezone for which the device was configured.

Here is where NodaTime library comes handy, powerful date and time library which also has PCL version (library is available on NuGet).

It this example we expect that DateTime data comes from server in UTC format. Pros for storing DateTime in UTC are numerous. You can familiarize yourself with Time Zones best practices here.


First we will implement IValueConverter which will be used from XAML markup. Our UtcToZonedDateTimeConverter should implement Convert and ConvertBack methods.

Convert method should receive DateTime object as value and TimeZoneId as parameter.
Method is expecting DateTime object in UTC format (even though its Kind may not be set to UTC explicitly).
TimeZoneIds should be in IANA format.
If parameters are correct, we will obtain TimeZone object and use it to convert DateTime to specified time zone.

ConvertBack method in similar manner converts time zoned DateTime back to DateTime in UTC format.

XAML markup

In XAML file we will load Converter as resource:

Once converter is available we are ready to use it as static resource to convert bound DateTime property:

With this kind of implementation we have functional time zone converter which could be easily used in XAML views whenever needed.

Check out working example on my GitHub repository.

Sharing is caring!

Leave a Reply

Your email address will not be published. Required fields are marked *