Last year at a local conference I gave a talk on topic “Xamarin Forms Application Performance Through Memory Management”. One of the examples I presented was occurrence of memory leak when using Acr SignaturePad control, which caused Out of Memory exception on Android after 10-15 signings. In the meantime the control became obsolete as Xamarin introduced the new version of their SignaturePad control which now supports Xamarin.Forms. Unfortunately memory leak is still an open issue on GitHub that bothers many developers. The issue is deeply rooted in the way how Xamarin framework handles memory management. I highly recommend you to […]
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 […]
SwipeCardView is a lightweight MVVM friendly user control that brings Tinder-style swipe card view into Xamarin.Forms applications. In this blog post I will talk about card based user interfaces and why they are better than newsfeeds, with the special attention to Tinder approach. Then I will cover in detail the design and the implementation of SwipeCardView. If you are not interested in the background nor implementation details, feel free to jump to the usage example of this PCL library, which is available on NuGet and GitHub.
Imagine you have an enterprise application running on hundreds or thousands of mobile devices in field. Your application is being used every day, and it is rarely being restarted (users prefer leaving the application in the foreground all the time). While we all tend to create applications that are memory responsible, the reality is that there would be memory leaks. With intensive usage of the application described in the example above, even small memory leaks would eventually cause the issues (application malfunctions or breaks). Our Android application is developed using Xamarin.Forms. Our server runs on Azure and exposes REST API […]