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

Profiling with Hierarchy Viewer


Hierarchy Viewer provides a powerful profiler to analyze and optimize the application. To proceed with the profiling, click the icon, Profile Node. If the hierarchy of your view is quite large, it might take some time until it is initialized.

At this point, all the views in your hierarchy will get three dots:

  • The left dot represents the Draw process of the rendering pipeline

  • The middle dot represents the Layout phase

  • The right dot represents the Execute phase

Each dot color within a view has a different meaning:

  • A green dot means that the view is rendering faster than at least half of the other views. Generally, a green color can be seen as a high-performing view.

  • A yellow dot means that the view is rendering faster than the bottom half of the views in the hierarchy. This is only relative, but yellow colors might require us to take a look at the view.

  • Red means the view is among the slowest half of views. Generally, we want to take a look at these values.

How can...