Prism.Forms is a powerful framework for building Xamarin.Forms application. It is very well-know in the Xamarin Community. If you are interested in exploring the framework, or if you are already using Prism.Forms and would like to explore new releases, perhaps you are a product owner and would like to test out Prism.Forms APIs with your product, or you are a community contributor who would like to learn, share, teach, blog or speak on Prism.Forms, Prism.Forms Gallery is for you. Prism.Forms Gallery demonstrates a number of Prism and Prism.Forms features in a single app.Continue reading
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.
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.
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.