Book Image

Android High Performance Programming

By : Emil Atanasov, Enrique López Mañas, Diego Grancini
Book Image

Android High Performance Programming

By: Emil Atanasov, Enrique López Mañas, Diego Grancini

Overview of this book

Performant applications are one of the key drivers of success in the mobile world. Users may abandon an app if it runs slowly. Learning how to build applications that balance speed and performance with functionality and UX can be a challenge; however, it's now more important than ever to get that balance right. Android High Performance will start you thinking about how to wring the most from any hardware your app is installed on, so you can increase your reach and engagement. The book begins by providing an introduction to state–of-the-art Android techniques and the importance of performance in an Android application. Then, we will explain the Android SDK tools regularly used to debug and profile Android applications. We will also learn about some advanced topics such as building layouts, multithreading, networking, and security. Battery life is one of the biggest bottlenecks in applications; and this book will show typical examples of code that exhausts battery life, how to prevent this, and how to measure battery consumption from an application in every kind of situation to ensure your apps don’t drain more than they should. This book explains techniques for building optimized and efficient systems that do not drain the battery, cause memory leaks, or slow down with time.
Table of Contents (17 chapters)
Android High Performance Programming
Credits
About the Authors
About the Reviewer
www.PacktPub.com
Preface
Index

Chapter 6. Networking

While talking about performance in a mobile application, the main concern is how our application behaves in poor connectivity conditions. No developer wants his users to give negative feedback because the application is too slow while uploading or downloading data, or it is not synchronized with other platforms versions of the same application. How many times do we change the networking strategy of our application because a client or users said it is too slow? Networking is not completely controllable from the client side because too many external factors are involved in the process: proxies, web servers, service providers, DNSs, and so on. We cannot know if there is a problem in one or more of the elements of that chain.

Moreover, the user does not know where the problem is, but he will think the application is not good. Then he will uninstall it. Nevertheless, we can control the application behavior and improve the user-perceived performance of our application by using...