Book Image

Hands-On Android UI Development

By : Jason Morris
Book Image

Hands-On Android UI Development

By: Jason Morris

Overview of this book

A great user interface (UI) can spell the difference between success and failure for any new application. This book will show you not just how to code great UIs, but how to design them as well. It will take novice Android developers on a journey, showing them how to leverage the Android platform to produce stunning Android applications. Begin with the basics of creating Android applications and then move on to topics such as screen and layout design. Next, learn about techniques that will help improve performance for your application. Also, explore how to create reactive applications that are fast, animated, and guide the user toward their goals with minimal distraction. Understand Android architecture components and learn how to build your application to automatically respond to changes made by the user. Great platforms are not always enough, so this book also focuses on creating custom components, layout managers, and 2D graphics. Also, explore many tips and best practices to ease your UI development process. By the end, you'll be able to design and build not only amazing UIs, but also systems that provide the best possible user experience.
Table of Contents (21 chapters)
Title Page
Credits
About the Author
About the Reviewers
www.PacktPub.com
Customer Feedback
Preface
13
Activity Lifecycle

Creating a RecyclerView adapter


In order to get data into a RecyclerView, you need an Adapter class, not unlike the PagerAdapter you wrote to display the attachment previews for the CaptureClaimActivity. However, RecyclerView does a lot more of the heavy lifting than ViewPager and as a result, what you can and can't do inside the adapter is far more restricted than with PagerAdapter. Also, unlike a PagerAdapter, a RecylcerView adapter has two actions that are involved in displaying each element: create and bind. When the RecyclerView needs a new child widget for an element, it will invoke onCreateViewHolder, which should return an unpopulated ViewHolder, which will then be passed to onBindViewHolder where the data should be mapped into the View from whatever data source the adapter uses.

First off, the RecyclerView maintains the list of its child views completely, so the adapter must never add or remove them directly. Secondly, the RecyclerView expects the adapter to be stable, that is, the...