1 views collected around this technical thread.
This article details three major optimization directions—component scheduling, component reuse, and component governance—applied to Taobao live streaming, explaining the technical redesign, task scheduler implementation, RecyclerView view‑holder reuse, performance gains, and future improvement plans.
The article demonstrates how to create a lightweight, infinite‑scrolling danmu (bullet‑screen) effect in Android by embedding a RecyclerView inside a custom DanMuView, using StaggeredGridLayoutManager for multi‑row layout and a scrollBy‑based Runnable to continuously scroll and control speed.
The article explains how to implement a performant, draggable grid in Android by using RecyclerView with ItemTouchHelper, detailing event interception, view translation via matrix or translation properties, efficient data swapping, custom item decorations for spacing, and handling drawing order for older Android versions.
This article explains how to build a two-level comment system for an Android app by designing a comment database schema, creating DAO and repository layers, and using nested RecyclerViews with adapters to display primary comments and their replies, including code snippets and layout illustrations.
This article explains the OffscreenPageLimit attribute of ViewPager2, how it controls off‑screen page loading, compares its default values with ViewPager, shows code implementations, analyzes performance trade‑offs, and provides practical recommendations for choosing an appropriate limit.
This article introduces HorStickyNavLayout, a custom Android ViewGroup that enhances RecyclerView horizontal scrolling with a sticky footer prompting users to discover more content, detailing its architecture, nested scrolling handling, fling behavior, and animation logic to improve interaction without extra item views.
The article explains why reporting item exposure in onBindViewHolder is inaccurate, reviews existing scroll‑listener based solutions and their limitations, and then presents a layout‑manager‑independent Kotlin extension that reliably detects RecyclerView item visibility based on visible area percentage, also covering ViewPager2 page visibility handling.
The paper presents a React Native‑based dynamic list solution that embeds an RN container inside Android RecyclerView ViewHolders, using data‑driven rendering and pre‑loaded offline bundles to achieve middle‑to‑upper performance, modest memory use, and sub‑0.01% error rates while preserving native first‑screen speed.
This article explains how to embed Jetpack Compose within an existing RecyclerView using ComposeView, examines the default DisposeOnDetachedFromWindow strategy, its impact on view recycling, and presents alternative composition strategies such as DisposeOnViewTreeLifecycleDestroyed and the newer pooling-aware strategy to improve performance.
This article demonstrates how to simplify and decouple a complex Android RecyclerView adapter by extracting view‑holder logic into a sealed BaseVH class, automatically registering subclasses via Kotlin reflection, and optionally replacing the whole approach with Jetpack Compose.
This article describes how the Lofter team applied Domain‑Driven Design to refactor and govern complex, multi‑type RecyclerView lists on Android, progressing from a monolithic adapter through a split‑stage implementation to a full DDD‑based framework with reusable bars and context‑aware layout managers.
By preloading off-screen items, applying a short non-animated jump for large distances, and then using a customized smooth-scroll with precise offset correction, the Android RecyclerView achieves fast, accurate scrolling without white-screen flashes or abrupt stops, greatly improving navigation of long, dynamically-sized lists.
This document presents the background, objectives, research findings, design principles, API specifications, caching strategy, implementation details, XML usage, memory impact analysis, and conclusions of a unified rich‑media animation component that consolidates image, GIF, Lottie, pager and video handling for efficient reuse in Android RecyclerView lists.
The article details how refactoring the Haokan Android short‑video client from a single global player to per‑holder multi‑player instances, combined with lifecycle‑lite event handling, pre‑loading, and dedicated thread operations, cut start‑up latency by ~150 ms, reduced frame‑drops dramatically, and boosted overall user experience and business metrics.
This article analyzes the limitations of traditional Android exposure tracking methods that rely on parent container lifecycles and introduces a reusable, low-intrusion solution using a custom layout that leverages core View lifecycle callbacks and drawing listeners to accurately detect component visibility and duration.
This article describes how the Snowball Android team solved the slow‑frame issue on the fund detail page by implementing a split‑screen loading layout using RecyclerView, CoordinatorLayout, and ViewPager, focusing on achieving a linked scrolling effect for the bottom discussion overlay through custom BottomSheetBehavior extensions and nested scrolling mechanisms.
This article presents a comprehensive solution for tracking and reporting exposure of RecyclerView items in Android, covering data collection during scrolling, visibility changes across fragment and activity lifecycles, handling data updates, and providing customizable callbacks and exposure criteria, all without requiring developers to manage the collection process manually.
This article analyzes why StaggeredGridLayoutManager can cause item reordering and blank gaps at the top of a RecyclerView, explains the underlying measurement and layout mechanisms, and presents code‑level solutions such as disabling gap handling, invalidating span assignments, and using notifyItemRangeChanged instead of notifyDataSetChanged.
This article explains the Android NestedScrolling mechanism, compares it with the traditional view event dispatch system, details the core scrolling flow, presents the key NestedScrollingParent and NestedScrollingChild interfaces with code examples, and walks through a practical demo and source‑level analysis.
This article proposes a solution to avoid data inconsistency caused by RecyclerView ViewHolder reuse by giving each ViewHolder its own lifecycle, integrating MVVM via a BaseLifecycleViewHolder, BaseLifeCycleAdapter, and VHLiveData, and demonstrates implementation details with Kotlin and Java code examples.