Book Image

Mastering Xamarin UI Development - Second Edition

By : Steven F. Daniel
Book Image

Mastering Xamarin UI Development - Second Edition

By: Steven F. Daniel

Overview of this book

This book will provide you with the knowledge and practical skills that are required to develop real-world Xamarin and Xamarin.Forms applications. You’ll learn how to create native Android app that will interact with the device camera and photo gallery, and then create a native iOS sliding tiles game. You will learn how to implement complex UI layouts and create customizable control elements based on the platform, using XAML and C# 7 code to interact with control elements within your XAML ContentPages. You’ll learn how to add location-based features by to your apps by creating a LocationService class and using the Xam.Plugin.Geolocator cross-platform library, that will be used to obtain the current device location. Next, you’ll learn how to work with and implement animations and visual effects within your UI using the PlatformEffects API, using C# code. At the end of this book, you’ll learn how to integrate Microsoft Azure App Services and use the Twitter APIs within your app. You will work with the Razor Templating Engine to build a book library HTML5 solution that will use a SQLite.net library to store, update, retrieve, and delete information within a local SQLite database. Finally, you will learn how to write unit tests using the NUnit and UITest frameworks.
Table of Contents (15 chapters)

Summary

In this chapter, we learned about the architecture behind the Xamarin.Forms Navigation API architecture, which provides us with a better method of performing navigation within the ViewModel. Then, we learned the differences between navigating using the Navigation and the ViewModel approaches.

You then learned how to create and implement a Navigation Interface and Class that will be used by each of our ViewModels to handle the navigation between our Views and ViewModels. We then updated our BaseViewModel class to include a property to our INavigationService interface.

Lastly, we updated each of our ViewModels to make use of the INavigation interface, as well as the code-behind files for each of our ContentPages that will implement the ViewModels, so that the bindable object properties defined within the XAML can be bound to those properties that are defined within the associated...