Book Image

Creating Cross-Platform C# Applications with Uno Platform

By : Matt Lacey, Marcel Alexander Wagner
Book Image

Creating Cross-Platform C# Applications with Uno Platform

By: Matt Lacey, Marcel Alexander Wagner

Overview of this book

Developers are increasingly being asked to build native applications that run on multiple operating systems and in the browser. In the past, this would have meant learning new technologies and making multiple copies of an application. But the Uno Platform allows you to use tools, languages, and APIs you already know from building Windows apps to develop apps that can also run on other platforms. This book will help you to create customer-facing as well as line-of-business apps that can be used on the device, browser, or operating system of your choice. This practical guide enables developers to put their C# and XAML knowledge to work by writing cross-platform apps using the Uno Platform. Packed with tips and practical examples, this book will help you to build applications for common scenarios. You'll begin by learning about the Uno Platform through step-by-step explanations of essential concepts, before moving on to creating cross-platform apps for different lines of business. Throughout this book, you'll work with examples that will teach you how to combine your existing knowledge to manage common development environments and implement frequently needed functionality. By the end of this Uno development book, you will have learned how to write your own cross-platform apps with the Uno Platform and use additional tools and libraries to speed up your app development process.
Table of Contents (13 chapters)
Section 1: Getting to Know Uno Platform
Section 2: Writing and Developing Uno Platform Apps
Section 3: Test, Deploy, and Contribute

Performing manual testing and why it is important

While automated tests help to find bugs and issues, there are certain things they cannot cover that still require manual testing. When developing apps that make use of features such as a camera, Bluetooth, or other device capabilities, writing automated tests is hard and sometimes even impossible. In these scenarios, manual testing is necessary. This is especially important with connectivity features to see how your app handles unstable connections and whether your app still provides a good user experience, especially with varying connection quality. More importantly, testing using emulators makes it hard to verify how the app will feel on actual devices, especially when thinking about the user experience, such as elements being the right size and easily tappable on screens.

In addition to testing specific features that are hard to simulate as part of an automated test such as GPS or roaming data access, manual testing is also critical...