# Fragment Published articles for Fragment. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Send RecyclerView's scroll events to a compose parent DevFeed: [Send RecyclerView's scroll events to a compose parent]() Original publisher: [Read original article]() Author: Leonidas Partsas Published: 2025-08-10T06:58:04Z Content type: tutorial Language: en Sources: [le0nidas]() Topics: [Compose](), [recyclerview](), [screen](), [App]() Tags: [android](), [app](), [compose](), [enter-always-behavior](), [featured](), [fragment](), [fragments](), [jetpack-compose](), [kotlin](), [nested-scroll](), [recyclerview](), [screen](), [top-app-bar]() ### AI overview This tutorial explains how to send RecyclerView scroll events to a Jetpack Compose parent during a gradual migration from fragment-based Android screens. It describes connecting Compose nested-scroll behavior to a RecyclerView using a NestedScrollDispatcher so a Compose top bar can respond to scrolling. ### Source excerpt We have an app that relies heavily on fragments. Every screen is an activity that hosts a fragment that hosts a recycler view: We want to start migrating the screens to compose by keeping the screen's content and placing it in a compose environment. This means that our activities will call setContent { } instead ... Continue reading Send RecyclerView's scroll events to a compose parent -> ## Jetpack Compose: A use case for view interop migration strategy - Jigar Brahmbhatt DevFeed: [Jetpack Compose: A use case for view interop migration strategy - Jigar Brahmbhatt]() Original publisher: [Read original article]() Published: 2023-02-08T12:00:26Z Content type: tutorial Language: en Sources: [Touchlab | Enterprise Mobile Innovation & Development]() Topics: [Jetpack Compose](), [migration](), [SDK](), [Android]() Tags: [android](), [compose](), [fragment](), [fragments](), [interop](), [jetpack-compose](), [layout](), [migration](), [navigation](), [redesign](), [sample](), [sdk](), [testing]() ### AI overview This article describes using Jetpack Compose with existing Android views and fragments during a sample app redesign for an SDK. It explains a Fragments-in-Compose approach, Compose navigation, SharedPreferences reuse, and adjustments needed for UI testing. ### Source excerpt We had an opportunity to redesign the sample app for an SDK we're developing, using Jetpack Compose as part of our interop migration strategy. ## Fragment Lifecycles in the Age of Jetpack DevFeed: [Fragment Lifecycles in the Age of Jetpack]() Original publisher: [Read original article]() Author: Márton Braun Published: 2020-06-18T16:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [Jetpack](), [android-development](), [Android](), [ui](), [configuration](), [Coroutines](), [App](), [Dark Mode]() Tags: [android](), [android-development](), [code](), [configuration](), [coroutines](), [dark-mode](), [fragment](), [fragments](), [jetpack](), [kotlin](), [lifecycle](), [livedata](), [marton-braun](), [scope](), [ui](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview This article explains Android Fragment lifecycles in the Jetpack ecosystem, covering the Fragment instance lifecycle and the nested view lifecycle. It describes recreation during state restoration, configuration changes, and process death, along with lifecycle methods, state handling, and resource management. ### Source excerpt Fragments have... Complicated lifecycles, to say the least. Let's take a look at these, and how they all fit into the world of Jetpack today, with LifecycleOwners, LiveData, and coroutines. ## Let's Review: Pokedex DevFeed: [Let's Review: Pokedex]() Original publisher: [Read original article]() Author: Márton Braun Published: 2020-01-07T14:00:00Z Content type: article Language: en Sources: [zsmb.co]() Topics: [Code review](), [Android](), [Development](), [Jetpack](), [Framework](), [implementation](), [ui]() Tags: [android](), [android-development](), [android-jetpack](), [code-review](), [fragment](), [implementation](), [kotlin](), [marton-braun](), [project](), [pull-request](), [repository](), [review](), [viewmodel](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview A code review of the Pokedex Android side project examines its project structure, code organization, formatting, imports, and use of Android Jetpack components and lifecycles. The review is presented as a learning resource for developers. ### Source excerpt In what may be the start of a new series, I code review a project that was posted on reddit recently and got very popular very quickly. Let's see what we can learn from it? ## Understanding Fragment Transactions and Back Navigation DevFeed: [Understanding Fragment Transactions and Back Navigation]() Original publisher: [Read original article]() Author: info@jeroenmols.com (Jeroen Mols) Published: 2017-12-18T00:00:00Z Content type: tutorial Language: en Sources: [Jeroen Mols]() Topics: [Transactions](), [navigation](), [App](), [implementation]() Tags: [android](), [app](), [blogs](), [events](), [fragment](), [fragments](), [implementation](), [login](), [navigation](), [rewrite](), [screen](), [transactions]() ### AI overview This tutorial investigates unexpected Android Fragment behavior when login-related Fragment transactions interact with back navigation. It explains that the transaction manager saves executed transactions rather than the Fragments themselves, which can leave multiple Fragments visible after navigating back. ### Source excerpt Do Fragment transactions and back navigation have no more secrets for you? Well then you should try to solve the mystery in this post, where a Fragment (literally) came to haunt us... ## How Fragment for Android Asks Users for Ratings and Reviews DevFeed: [How Fragment for Android Asks Users for Ratings and Reviews]() Original publisher: [Read original article]() Published: 2014-09-05T07:00:00Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [App](), [ui]() Tags: [android](), [app](), [fragment](), [play-store](), [review]() ### AI overview The article explains how the Fragment for Android team designed a non-intrusive prompt for app ratings. It places a rating button in the interface rather than showing a generic dialog, and delays showing it until the app has been launched three times and the user reaches the Export screen. ### Source excerpt One of the most important factors in determining whether or not people will buy your app is the rating. Especially if your app isn't free, people will generally check the ratings and reviews before downloading your app. And if your app is a paid app, ratings and reviews can mean success or failure for your app. When launching Fragment for Android, our first though was making a kick ass app, but then we needed to think about how to ensure that users remembered to go back to the Play Store to share their experience by rating the app. It's quite common for apps to display a generic dialog after a while prompting the user to rate the app, but we thought we could make this experience better. ## Bringing Fragment to Android DevFeed: [Bringing Fragment to Android]() Original publisher: [Read original article]() Published: 2014-08-21T07:00:00Z Content type: opinion Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [iOS](), [ui](), [User Experience](), [Google Play](), [App]() Tags: [android](), [apps](), [fragment](), [google-play](), [ios](), [ui](), [user-experience]() ### AI overview The article describes bringing Pixite's iOS photo app Fragment to Android. It discusses studying the iOS design and adapting platform-specific interactions, including removing redundant "X" buttons and changing the export screen to use Android's sharing capabilities. ### Source excerpt In November 2013, Ben Guerrette from Pixite reached out to me after reading my post about my experience being featured on the Google Play. He was interested in bringing one of their iOS photo apps to Android. At this point I wasn't familiar with Pixite, so I promptly fired up the Google to do my research. I was quite impressed with what I found. The guys at Pixite had created some really cool photo apps for iOS, and when I searched Google Play for similar offerings on Android, I found next to nothing. ## The case for Fragment Callbacks DevFeed: [The case for Fragment Callbacks]() Original publisher: [Read original article]() Published: 2013-02-18T07:00:00Z Content type: article Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [interfaces](), [Code](), [Development]() Tags: [android](), [api](), [fragment](), [google](), [google-i-o](), [interface](), [interfaces]() ### AI overview This article recommends using callback interfaces for communication between Android Fragments and their parent activities. It argues that casting the parent activity creates tightly coupled code, while callbacks improve reuse, maintainability, flexibility, and separation of responsibilities. ### Source excerpt Fragment are a great addition to Android. They allow reusability of sections of your views at the controller layer, and they also provide better encapsulation of your app's logic. This can really help developers speed up code development and also keep their code clean, which makes it easier to maintain. All of these benefits are available if you follow a few guidelines when developing your code. One of the biggest mistakes that I see developers make, particularly those coming from other platforms, is casting the parent activity. The Fragment API provides methods for communicating with the parent activity because there are many things, like navigation, that should not be handled by the Fragment. This requires a mechanism for the Fragment to notify the parent Activity when certain activities occur.