Reactive RecyclerViews: Moving from "Manual" to "Automatic"

 Stop calling adapter.submitList() in Fragments. Use Data Binding + Binding Adapters to build clean, declarative RecyclerView UIs.

Reactive RecyclerViews: Moving from "Manual" to "Automatic"

Most Android developers update their lists like this:

viewModel.items.observe(viewLifecycleOwner) { list ->
    adapter.submitList(list)
}

It works, but it’s “manual transmission.” Every new list requires a new observer, cluttering your Fragment and coupling your UI logic to the lifecycle owner. By shifting to Data Binding + Binding Adapters, we achieve a truly declarative UI.

The Architecture Flow

Instead of your Fragment acting as a middleman, the data flows in a direct, reactive stream:

ViewModel → LiveData / StateFlow → Data Binding → BindingAdapter → RecyclerView

🛠 The Secret Sauce: A Type-Safe Binding Adapter

We want a bridge that is reusable and crash-proof. Using Kotlin generics ensures our adapter handles any data type safely without risky manual casting.

object RecyclerViewBinding {

    @JvmStatic
    @BindingAdapter("items") // Attribute used in XML
    fun <T> setRecyclerViewItems(recyclerView: RecyclerView, items: List<T>?) {
        val adapter = recyclerView.adapter
        
        // 💡 Type-safe check: only submit if it's a ListAdapter
        if (adapter is ListAdapter<T, *>) {
            adapter.submitList(items)
        } 
    }
}

The XML Implementation

Your XML now becomes a map of your UI state. Just remember to wrap your layout in <layout> tags to enable Data Binding:

<androidx.recyclerview.widget.RecyclerView
    android:id="@+id/userRecyclerView"
    android:layout_width="match_parent"
    android:layout_height="match_parent"
    app:items="@{vm.userList}" 
    app:isVisible="@{vm.userList.size() > 0}" />

💡 Pro Tip: Order of Operations

Always set your RecyclerView adapter in your onCreateView (or onViewCreated) before the data is bound. If the BindingAdapter fires while the adapter is still null, it will skip the update, and you might miss the initial data emission from your ViewModel.

❌ When NOT to use this

While powerful, this pattern isn’t a silver bullet. Avoid it if:

  • High-Frequency Updates: For real-time data (like stock tickers), keeping the observer in the Fragment offers finer control over diffing timing.
  • Complex Side Effects: If updating the list requires immediate secondary actions (like triggering a specific animation or logging), a Fragment observer is easier to debug.

✨ Why This Matters

  • Cleaner Fragments: Your UI controller focuses on navigation and DI, not boilerplate plumbing.
  • Encapsulation: The logic for how a list updates stays in the BindingAdapter.
  • Scalability: Adding features like “Empty States” becomes a declarative one-liner in XML.

🙋‍♂️ Frequently Asked Questions (FAQs)

Does this work with StateFlow?

Yes, but ensure you’ve set the binding.lifecycleOwner. You may also need to call .asLiveData() in the ViewModel or use a version of Data Binding that natively supports Flow collection.

Does this impact performance?

The overhead is negligible. Data Binding is generated at compile-time, and using ListAdapter ensures that the heavy lifting (diffing) happens on a background thread.

💬 Over to You!

  • Do you prefer keeping UI logic in the Fragment for visibility, or in XML for cleanliness?
  • What’s the most complex BindingAdapter you’ve written?
  • How do you handle empty states in your RecyclerViews?

Drop your thoughts in the comments! 👇

This pattern doesn’t eliminate observers — it relocates them. Your UI becomes declarative, your Fragments thinner, and your update logic reusable across the entire app.

📘 Master Your Next Technical Interview

Since Java is the foundation of Android development, mastering DSA is essential. I highly recommend “Mastering Data Structures & Algorithms in Java”. It’s a focused roadmap covering 100+ coding challenges to help you ace your technical rounds.

Comments

Post a Comment

Popular posts from this blog

No More _state + state: Simplifying ViewModels with Kotlin 2.3

Image
 Clean up your Android code with Explicit Backing Fields—the modern way to handle read-only state without the boilerplate. TL;DR:  Kotlin 2.3 introduces  explicit backing fields , allowing you to replace the classic  _state  +  state  boilerplate with a single, cleaner property—provided you're okay with a few experimental trade-offs. If you’ve been developing Android apps, you know the “Backing Property Dance.” It’s that repetitive ritual where we create a private  MutableStateFlow  and a public  StateFlow  just to ensure encapsulation. The “Old” Way (The Boilerplate) private val _uiState = MutableStateFlow(UiState.Loading) // Exposing a read-only view of the mutable internal state val uiState: StateFlow<UiState> = _uiState.asStateFlow() We’ve done this for years to prevent external classes from mutating our state. While effective, it pollutes our IDE suggestions with underscores and adds unnecessary ceremony to every singl...
Read more

Why You Should Stop Passing ViewModels Around Your Compose UI Tree 🚫

Image
 Master State Hoisting and the "Route-level" pattern to build scalable, testable, and preview-friendly Android apps. If you’ve been building with Jetpack Compose for a while, you know how tempting it is to just pass a  ViewModel  instance down through five layers of UI components. It’s convenient—one object gives you all the data and all the functions you need. But here is the architectural reality:  Passing ViewModel instances deep into your UI tree is an architectural anti-pattern.  It couples your visual components to business logic and makes your code significantly harder to maintain, test, and preview. The Core Problem: Lifecycle and Scoping ViewModels are designed to be state holders tied to a specific lifecycle (usually a Navigation Destination). When you pass a ViewModel into a small UI component, you break the  Unidirectional Data Flow (UDF) . ❌ The “Bad” Way (Tight Coupling) // ❌ BAD: This component is now impossible to preview or reuse @Composabl...
Read more

Is Jetpack Compose Making Your APK Fatter? (And How to Fix It)

Image
 Unpacking the Compose Tax, compiler-driven DEX optimization, and why your resource strategy must evolve for modern UI. TL;DR DEX Bloat:  Compose’s compiler injects “Restartable” and “Skippable” logic for memoization; R8 minification is effectively required. Code vs. Assets:  Moving iconography to  ImageVector  constants allows R8 to prune unused assets as code. Tooling Leak:   ui-tooling  in release builds is the #1 cause of "false" bloat. The Scale Factor:  Compose has a higher “size floor” but a much lower “size ceiling” than the legacy View system. The promise of Jetpack Compose was simple: “Write less code, ship faster.” But as teams migrate, a quiet concern often echoes in code reviews:  “Why did our APK size just jump?” While Compose removes the weight of deep XML hierarchies and the overhead of ViewBinding, it introduces a unique “Compose Tax.” For a senior engineer, the goal isn’t just to accept this tax, but to optimize the runtime...
Read more