Book Image

Hands-On Mobile Development with .NET Core

By : Can Bilgin
Book Image

Hands-On Mobile Development with .NET Core

By: Can Bilgin

Overview of this book

.NET Core is the general umbrella term used for Microsoft’s cross-platform toolset. Xamarin, used for developing mobile applications, is one of the app model implementations for .NET Core infrastructure. In this book, you'll learn how to design, architect, and develop attractive, maintainable, and robust mobile applications for multiple platforms, including iOS, Android, and UWP, with the toolset provided by Microsoft using Xamarin, .NET Core, and Azure Cloud Services. This book will take you through various phases of application development using Xamarin, from environment setup, design, and architecture to publishing, with the help of real-world scenarios. Throughout the book, you'll learn how to develop mobile apps using Xamarin, Xamarin.Forms, and .NET Standard. You'll even be able to implement a web-based backend composed of microservices with .NET Core using various Azure services including, but not limited to, Azure App Services, Azure Active Directory, Notification Hub, Logic Apps, Azure Functions, and Cognitive Services. The book then guides you in creating data stores using popular database technologies such as Cosmos DB, SQL, and Realm. Finally, you will be able to set up an efficient and maintainable development pipeline to manage the application life cycle using Visual Studio App Center and Visual Studio Services.
Table of Contents (26 chapters)
Title Page
Copyright and Credits
About Packt
Contributors
Preface
Index

Utilizing tasks and awaitables


User experience (UX) is a term that is used to describe the composition of UI components and how the user interacts with the UI components. In other words, UX is not only how the application is designed, but rather the impression of the user about the application. In this context, the responsiveness of the application is one of the key factors that defines the quality of the application.

In general terms, a simple interaction use case starts with user interaction. This interaction can be a tap on a certain area on the screen, a certain gesture on a canvas, or an actual user input in an editable field on the screen. Once the user interaction triggers the execution flow, the application business logic is responsible for updating the UI to notify the user about the result of their input.

As you can see, in the asynchronous version of the simple interaction model, the application starts the execution of the designated business flow and doesn't wait for it to complete...