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)

Project overview

This project will be to set up the backend for a chat application. The biggest part of the project will be the configuration that we will carry out in the Azure portal. We will also write some code for the Azure Functions that will handle the SignalR connections. There will be one function to return information about the SignalR connection and one that posts messages to the SignalR service. The function that we will post messages to will also determine whether the message contains an image. If it does, it will be sent to the Vision API in Azure Cognitive Services to analyze whether it contains adult content. If it does, it won't be posted to the SignalR service and the other users will not get it. Because the SignalR service has a limitation about how big messages can be, we need to store images in blob storage and just post the URL of the image to the users...