The code you write today will suck tomorrow, and it should. So I've learned this a lot lately when writing Xamarin projects especially. Applications I've written at the time I thought were clean
So I have started a Nuget package for Xamarin. This package is to help prevent me from constantly reinventing the wheel when possible. For example, it includes several IValueConverters such as IsNull, IsNotNull,
So James Montemagno has written a plugin a long while back that provides an easy method for writing images to XAML. The only down side to this is that you have to add
So why would you need to write a custom control for Xamarin? Does it have a purpose other than wrapping native controls that don’t exist in Xamarin? Why yes, it does serve
Explanation XAML isn’t perfect. It is often missing some tools that honestly should just be a party of the set. For example, express if a value is null or not null. What
If you are writing an application that has it’s authentication with JWT, you might be wondering what is a good method to do this? I’ve used the HttpClient along with Xamarin.
So I’ve written a few Xamarin projects now, and there have been a few things I’ve found that help keep your code clean. Disclaimer, this is based on my own opinion
So my friend Dylan had a site about his kids, that I lost on a really bad click during a stressed out moment. So for that I am really sorry. But I really