Book Image

Android Studio Cookbook

By : Mike van Drongelen
Book Image

Android Studio Cookbook

By: Mike van Drongelen

Overview of this book

This book starts with an introduction of Android Studio and why you should use this IDE rather than Eclipse. Moving ahead, it teaches you to build a simple app that requires no backend setup but uses Google Cloud or Parse instead. After that, you will learn how to create an Android app that can send and receive text and images using Google Cloud or Parse as a backend. It explains the concepts of Material design and how to apply them to an Android app. Also, it shows you how to build an app that runs on an Android wear device. Later, it explains how to build an app that takes advantage of the latest Android SDK while still supporting older Android versions. It also demonstrates how the performance of an app can be improved and how memory management tools that come with the Android Studio IDE can help you achieve this. By the end of the book, you will be able to develop high quality apps with a minimum amount of effort using the Android Studio IDE.
Table of Contents (17 chapters)
Android Studio Cookbook
About the Author
About the Reviewers

Memory profilers and performance tools

Your app could suffer from memory leaks or from allocating too much memory.

The Garbage Collector (GC), responsible for cleaning up anything we do not want to use any more, is a great helper, but unfortunately, it is not perfect. It can only remove objects that are recognized as unreachable. Objects that are not cleaned up just hang around taking up space. After a while, if more and more objects are created, an OutOfMemoryError could occur, as would be the case if a couple of large images are attempted to load, which is a commonly seen crash scenario for many Android apps.

Memory leaks are somewhat difficult to find. Luckily for us, Android Studio comes with a memory monitor. It gives you an overview of your app's memory usage and some clue about memory leaks.

We will be using this Memory monitor to find out whether unwanted GC event patterns are causing performance issues. In addition to this, we will use Allocation Tracker to identify where in the code...