Book Image

Learning Android Application Development

By : Raimon Ràfols Montane, Laurence Dawson
Book Image

Learning Android Application Development

By: Raimon Ràfols Montane, Laurence Dawson

Overview of this book

The mobile app market is huge. But where do you start? And how you can deliver something that takes Google Play by storm? This guide is the perfect route into Android app development – while it’s easy for new apps to sink without a trace, we’ll give you the best chance of success with practical and actionable guidance that will unlock your creativity and help you put the principles of Android development into practice. From the fundamentals and getting your project started to publishing your app to a huge market of potential customers, follow this guide to become a confident, creative and reliable mobile developer. Get to grips with new components in Android 7 such as RecyclerView, and find out how to take advantage of automated testing, and, of course, much, much more. What are you waiting for? There’s never been a better time – or a better way – to get into Android app development.
Table of Contents (16 chapters)
Learning Android Application Development
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface

Loading images


We have seen, so far, how to keep images in a local memory cache and in disk cache to avoid loading them from the network repeatedly in the quite common case when are used again. As mobile devices still have very limited resources, we will see how to deal with memory allocation and handling very large images.

Memory

As we have probably noticed, images take a big amount of space. For example, a 32 bit per pixel image 512 pixels wide and 512 pixels high will use around 1 megabyte of memory. So, having a lot of images can easily eat up all our memory. It is very important to take into consideration a few things when dealing with such amount of memory.

We don't really need to explain in detail how to manage bitmap memory on early releases of Android, as we will not probably have to support those versions, but just in case, it is good to know how it worked.

On Android 2.3.3 and lower versions, bitmap memory dedicated to store pixel data was stored in native memory and not in the Java...