• Preface
  • Prerequisites
  • Source Code and Its License
  • Creative Commons and the Four-to-Free (42F) Guarantee
  • Acknowledgments
• Room Basics
  • Room Requirements
  • Room Furnishings
  • Get a Room
• Testing Room
  • Writing Unit Tests via Mocks
• The Dao of Entities
  • DAOs and Queries
  • Dynamic Queries
  • Other DAO Operations
  • Transactions and Room
  • Threads and Room
• Room and Custom Types
  • Embedded Types
  • Updating the Trip Sample
• Room and Relations
  • A History of Threading Mistakes
  • The Room Approach
  • Plans for Trips
  • Self-Referential Relations for Tree Structures
  • Using @Relation
  • @Relation and @Query
  • Representing No Relation
• The Support Database API
  • When Will We Use This?
  • Configuring Room’s Database Access
• Room and Migrations
  • When Do We Migrate?
  • But First, a Word About Exporting Schemas
  • Writing Migrations
  • Employing Migrations
  • How Room Applies Migrations
  • Testing Migrations
• Lifecycles and Owners
  • Adding the Lifecycle Components
  • Getting a Lifecycle
  • Observing a Lifecycle
  • Legacy Options
  • So, What’s the Point of This?
• LiveData
  • Yet More Terminology
  • Implementing LiveData
  • Other LiveData Examples
• ViewModel
  • ViewModel Versus…
  • Dependencies
  • Mommy, Where Does a ViewModel Come From?
  • ViewModel In Action
• Other Lifecycle Owners
  • ProcessLifecycleOwner
  • Wait… Where Are LifecycleProvider and LifecycleReceiver?
• LiveData and Data Binding
  • LiveData Updating Data Binding
  • Handling Changes to LiveData
  • The Saved Instance State Situation
• WorkManager
  • Where Should We Not Use WorkManager?
  • WorkManager Dependencies
  • Workers: They Do Work
  • Performing Simple Work
  • Work Inputs
  • Constrained Work
  • Tagged Work
  • Monitoring Work
  • Canceling Work
  • Delayed Work
  • Parallel Work
  • Chained Work
  • Periodic Work
  • Unique Work
  • Testing Work
  • WorkManager and Side Effects
• M:N Relations in Room
  • Implementing DAO Methods
  • Where’s That Good Ol’ Object Feel?
• Polymorphic Room Relations
  • Polymorphism With a Single Table
  • Polymorphism With M:N Relations
• LiveData Transformations
  • Mapping Data to Data
  • Mapping Data to… LiveData?
  • Writing a Transformation
  • Do We Really Want This?
• RxJava and Room
  • Decisions, Decisions
  • The One-Time Option: Single
  • The One-Time 0-1 Option: Maybe
  • The Ongoing Option: Flowable
  • @RawQuery and Reactive Responses
• RxJava and Lifecycles
  • Bridging RxJava and LiveData
  • The Uber Solution: AutoDispose
• Packing Up a Room
  • The Classic Solution: SQLiteAssetHelper
  • The New Problem
  • Merging SQLiteAssetHelper with Room
• Paging Room Data
  • Addressing the UX
  • Enter the Paging Library
  • Paging and Room
  • What About RxJava?
• LiveData and Bound Services
  • Remote Sensors
• Immutability
  • The Costs of Immutability
  • Immutability via AutoValue
• The Repository Pattern
  • High-Level Repository Strategies
  • Let’s Roll the Dice
  • Blending Data Sources
• Introducing Model-View-Intent
  • Why People Worry About GUI Architectures
  • Why Others Ignore GUI Architectures
  • A Rough Comparison of GUI Architectures
  • The Basics of Model-View-Intent
  • Additional MVI Resources
• A Deep Dive Into MVI
  • MVI and the Sample App
  • The Model
  • The View State
  • The View
  • The Actions
  • Publishing Actions
  • The Repositories
  • The Controller
  • About Those Results
  • The Reducer in the RosterViewModel
  • Examining the Other Fragments
  • Summary
• Backing Up a Room
  • Beware of Open Rooms
  • When Do We Back Up the Database?
  • A Basic Backup Example
  • Backing Up Off-Device
• Room and Full-Text Searching
  • The Room 1.x FTS Recipe
  • Searching a Book
• Room and Conflict Resolution
  • Fail
  • Ignore
  • Replace
  • Rollback
  • What Should You Use with Room?
• Configuring SQLite Beyond Room
  • Example: Turbo Boost Mode

---

This book is licensed under the Creative Commons Attribution-ShareAlike 4.0 International license.