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

Walkthrough


Before we get into the code, studying different techniques to improve our strategy, we want to give a general overview of networking and the possibilities the Android platform provides. So, let's think about what a client needs to do before retrieving the expected response from a server instance. When a client needs a server response, it is routed in a high-level architecture that contains many actors, such as Wi-Fi access points, LANs, proxies, servers, and DNS servers, with multiple instances of them and multiple requests to be fulfilled before getting back the desired response. Then, when the server receives the request, it needs to elaborate the response that has to be routed back to the client. The time it takes to do all of these operations needs to be reasonable for the user. Furthermore, one of the links between any two actors of the chain may be interrupted and then no response can be given back to the client. In the meantime, the user is waiting for a result on the...