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
About the Authors
About the Reviewer

We have already seen some basic possibilities that the file offers us. In reality, this file is similar to a GNU makefile: it describes the sources and shared libraries to the build system.

In the file, we can group all our resources into modules. Modules are static libraries, standalone executables, or shared libraries. The concept is also similar to the modules within Android Studio, which should be familiar to the reader by now. The same source can be used in different modules.

We have seen the following line in the previous script:

include $(CLEAR_VARS)

This value is automatically provided by the build system. This points to an internal makefile that it is in charge of cleaning many of the locals variables used.

We need to add the modules later on:

LOCAL_MODULE := example-module

For the file to work properly, modules need to have a unique name and not have special characters or spaces.


NDK will automatically append the prefix lib to your module when it is...