Book Image

Mastering Cross-Platform Development with Xamarin

By : Can Bilgin, Miljenko Cvjetko, Paulo Ortins, Robert Hellestrae, Craig Dunn
Book Image

Mastering Cross-Platform Development with Xamarin

By: Can Bilgin, Miljenko Cvjetko, Paulo Ortins, Robert Hellestrae, Craig Dunn

Overview of this book

The main goal of this book is to equip you with the required know-how to successfully analyze, develop, and manage Xamarin cross-platform projects using the most efficient, robust, and scalable implementation patterns. This book starts with general topics such as memory management, asynchronous programming, local storage, and networking, and later moves onto platform-specific features. During this transition, you will learn about key tools to leverage the patterns described, as well as advanced implementation strategies and features. The book also presents User Interface design and implementation concepts on Android and iOS platforms from a Xamarin and cross-platform perspective, with the goal to create a consistent but native UI experience. Finally, we show you the toolset for application lifecycle management to help you prepare the development pipeline to manage and see cross-platform projects through to public or private release.
Table of Contents (19 chapters)
Mastering Cross-Platform Development with Xamarin
About the Authors
About the Reviewers

Extending forms

Even though the Xamarin.Forms framework provides an extensive set of customizable UI elements, in certain scenarios you might want to change how a certain control looks or behaves. Moreover, at times, providing an application-wide customization scheme can provide consistency and decrease redundancy. XAML markup infrastructure used in Xamarin.Forms provides various custom implementation scenarios.


When implementing certain UI patterns, view elements have to be declared independent of each other, and yet they have to carry the same design attributes, such as typography, layout properties, colors, and so on. Styles can be used in this situation to organize and re-use the element attributes.

Using ListView, the only view container defined would be the item data template, and the content items loaded from the data source will be rendered using the same template. However, if the view requirement is to use Grid, StackLayout, or TableView, each view item would have to be defined...