Book Image

Xamarin.Forms Projects

By : Johan Karlsson, Daniel Hindrikes
Book Image

Xamarin.Forms Projects

By: Johan Karlsson, Daniel Hindrikes

Overview of this book

Xamarin.Forms is a lightweight cross-platform development toolkit for building applications with a rich user interface. In this book you'll start by building projects that explain the Xamarin.Forms ecosystem to get up and running with building cross-platform applications. We'll increase in difficulty throughout the projects, making you learn the nitty-gritty of Xamarin.Forms offerings. You'll gain insights into the architecture, how to arrange your app's design, where to begin developing, what pitfalls exist, and how to avoid them. The book contains seven real-world projects, to get you hands-on with building rich UIs and providing a truly cross-platform experience. It will also guide you on how to set up a machine for Xamarin app development. You'll build a simple to-do application that gets you going, then dive deep into building advanced apps such as messaging platform, games, and machine learning, to build a UI for an augmented reality project. By the end of the book, you'll be confident in building cross-platforms and fitting Xamarin.Forms toolkits in your app development. You'll be able to take the practice you get from this book to build applications that comply with your requirements.
Table of Contents (11 chapters)

Creating the matchmaking app

In this project, we will learn more about creating reusable controls that can be added to a XAML page. To keep things simple, we will not be using MVVM, but bare-metal Xamarin.Forms without any data binding. What we aim to create is an app that allows the user to swipe images, either to the right or the left, just like most popular matchmaking applications do.

Well, let's get started by creating the project!

Creating the project

Just as with the to-do list app in Chapter 2, Building our First Xamarin.Forms App, this chapter will start with a clean File | New Project approach. We are going to opt for a .NET Standard approach rather than a shared code approach in this chapter; please refer back...