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

Caching remote data


We have seen previously how to load images and display them in our application. But what happens when we have to load a huge amount of images? Let's imagine a List or a RecyclerView and the end user scrolling back and forth. As RecyclerView is recycling the views and replacing the bitmap with another, we would have to download  the same images from the Internet again and again. This is not only inefficient and slow, but it also drains the data plan and the user's battery. We can easily implement a cache to store the images so that we do not have to download them again and again. Let's see how we can do it.

Memory caches

The fastest way of accessing images is to store them in memory. We need to be careful as memory is a limited resource, and even more careful if we make assumptions, as every device has different amount of free memory. We will create a memory cache based on the amount of free memory and only use a small portion, leaving lots of memory for the app itself as...