Sign In Start Free Trial
Account

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Hands-On Android UI Development
  • Toc
  • feedback
Hands-On Android UI Development

Hands-On Android UI Development

By : Jason Morris
3.8 (4)
close
Hands-On Android UI Development

Hands-On Android UI Development

3.8 (4)
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 (15 chapters)
close
13
Activity Lifecycle

Wrapping up the category picker


The category picker you created for the CaptureClaimActivity is just a group of widgets in a card right now, and while it's one of the simplest cards to use on the screen, it's also one of the largest by the amount of code written for it. The best way to encapsulate this part of the screen is to move the layout that appears inside the CardView into a Fragment class.

However, why a Fragment class, and why not write another Layout class? Fragment classes are self-contained systems, and have their own life cycle within the context of their parent Activity. This means they can contain significantly more application logic, and can be reused more easily in other parts of the application. It's also because in this case, we rely on the IDs of the radio buttons to know what has been checked by the user, which means that we can very easily start polluting layouts with IDs specific to this specific widget. Fragment classes don't stop this from happening, but it's expected...

Unlock full access

Continue reading for free

A Packt free trial gives you instant online access to our library of over 7000 practical eBooks and videos, constantly updated with the latest in tech
bookmark search playlist download font-size

Change the font size

margin-width

Change margin width

day-mode

Change background colour

Close icon Search
Country selected

Close icon Your notes and bookmarks

Delete Bookmark

Modal Close icon
Are you sure you want to delete it?
Cancel
Yes, Delete