Xamarin.Forms is great. But, every now and then, it falls short on some basic modern controls e.g checkbox, radio buttons, cards, etc. Luckily, Xamarin community is large and very engaged with the platform. You can find plethora of custom controls or blogs on how to build custom controls for your project needs.
In recent years, I have created a bunch of custom controls that I am sure the community at large can benefit from. One such controls is a simple Checkbox. There are lots of implementations of checkbox available, but I wanted something simple and light, so I created one. Here’s how the checkbox works…
Code snippets are a hidden gem in Visual Studio that most of us do not pay much attention to. Utilizing them correctly can increase productivity when we have a lot to code. In Visual Studio, code snippets are available for multiple programming languages e.g. C#, F#, XML, HTML, CSS, Python, etc. They are extremely useful when we have a bunch of boiler plate code for our properties, constructors, bindable properties, etc.
Code snippets can be a huge topic, but in this post, I will list some of the XAML and C# code snippets useful when developing Xamarin.Forms mobile applications.
In this post,
- Creating Code Snippets
- C# Examples
- XAML Examples
- Export Templates
In this post, we will learn how to create a card view with child views using custom layouts. Creating a custom card unifies the experience for the user, gives us more control on the design of the app and speeds up the cross-platform UI/UX workflows. It is easy to get a simple, yet flexible, card introduced in your app.
Update: Get this card as part of IntelliAbb Xamarin Controls NuGet package.
When using a container for dependency injection in your Xamarin.Forms app, you may find yourself trying to use a plugin or library that is
static that you want to register with your container. Having
statics in our code makes it hard to test and causes coupling. In this post, I will demonstrate using Prism.Forms how to inject a
static plugin or library that may or may not expose an abstraction.
Android introduced BottomNavigationView in API 25.1 and I like it. To be honest, one of the biggest difference between iOS and Android for me was the placement of tabs. I enjoyed ActionBar tabs when they were a thing and loved the fact that I could swipe the tabs as I wished. But, when I used the bottom tabs in Android recently, I fell in love instantly. In today’s world of giant smartphones, one can only reach the bottom of the device during one-handed operations, so I loved the fact that I could use my hardware back button to navigate back and switch between tabs all with a single thumb.
If you are building a Xamarin.Forms app, it should be a no-brainer that you use MVVM pattern for your code base. It should also be a no-brainer that you give Prism.Forms a try. It makes development fast and code easy to maintain with its plethora of built-in services such for navigation, dependency injection, alerts, events, etc.
I recently added a sample to Prism’s samples library on how to use cross-platform EventAggregator using Prism.Forms in a Xamarin.Forms app.
Sometimes in this beautiful world of cross-platform mobile development, we come across a problem that makes no sense at first. But after some StackOverflow surfing and Xamarin/MSDN research, we may find a way to tackle that problem. In some scenarios, there are multiple solutions and we have to decide which approach works best given our situation. In this post, I will demonstrate one of these problems, rather scenarios. The multi-tap monstrosity on Android when using Xamarin.Forms.