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

RecyclerView


RecyclerView was introduced with Android 5.0 or Lollipop and was included directly in the support library, so it could be used in older versions of Android (we all know that firmware rollout is not always as fast as it should be because it might depend on operators and vendors). In this section, we will use the previous example to replace ListView with RecyclerView. We will see that it will take a bit more of code to set this up, but we will also be able to identify, quite clearly, its advantages: its flexibility and the uncoupling feature along with the ability to perform item layouts or item animation, helping us to keep a cleaner code architecture. In addition, RecyclerView was built with all the performance features we had to implement before in mind. This does not mean we do not have to do anything to implement them, but as we will see, the code is structured in a way that it will force us do to so naturally.

The official Android documentation defines it as a flexible view...