# Android framework Published articles for Android framework. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Chasing Monet inside the Android framework DevFeed: [Chasing Monet inside the Android framework]() Original publisher: [Read original article]() Author: Siddhesh Patil Published: 2022-04-27T23:50:55Z Content type: article Language: en Sources: [Sid Patil - Android Engineer and Kotlin Advocate]() Topics: [Android](), [Framework](), [material-you](), [Material Design](), [ui](), [color](), [aosp](), [android-13]() Tags: [android](), [android-12](), [android-13](), [android-framework](), [android-open-source-project](), [android-system-ui](), [aosp](), [article](), [articles-by-sid-patil](), [color](), [deep-dive](), [design](), [design-system](), [dynamic-colors-jetpack-compose](), [dynamic-theming](), [dynamic-theming-on-android](), [framework](), [how-does-dynamic-theming-work-on-android](), [internals](), [kotlin](), [material-design](), [material-design-3](), [material-you](), [md3](), [monet](), [monet-in-aosp](), [monet-theme-engine](), [monet-theming](), [pixel](), [system-ui-apk](), [tiramisu](), [ui]() ### AI overview A technical deep dive into Monet, the Android framework changes behind Android 12/12L dynamic theming and Material You. It explains how System UI responds to wallpaper changes, extracts colors, generates tonal palettes, and refreshes the system context. ### Source excerpt We deep dive into the internals of the Android framework, covering the System-UI to understand the changes introduced starting from Android 12/12L and above, code-named Monet. We will explore the new system-wide dynamic theming capabilities and take a look at how Monet fuels the Material You design. ## Easy Android Scopes DevFeed: [Easy Android Scopes]() Original publisher: [Read original article]() Published: 2020-03-13T16:09:47Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [configuration](), [Dagger](), [multiplatform]() Tags: [android](), [android-framework](), [cache](), [configuration](), [dagger](), [deprecated](), [fragments](), [lifecycle](), [multiplatform]() ### AI overview This tutorial examines how to scope Android objects across lifecycle changes, especially when Activities and Fragments are recreated during configuration changes. It discusses retaining presenters and extending lifecycle-bound retention to objects such as Dagger Components, while noting the limitations of the deprecated onRetainNonConfigurationInstance approach. ### Source excerpt A common challenge when writing Android apps is properly scoping objects: if they outlive the lifecycle in which they're needed then we are wasting memory and they can be leaked, but if we recreate objects too soon then we could be duplicating work when we don't need to. The most common place that this manifests in is Activities and Fragments, since they're destroyed and replaced by a new instance during events like configuration changes, which can be unintuitive, at first. ## ViewModel. How it works. DevFeed: [ViewModel. How it works.]() Original publisher: [Read original article]() Author: Vladislav Puryev Published: 2020-01-18T15:40:09Z Content type: tutorial Language: en Sources: [Stories by Vladislav Puryev on Medium]() Topics: [Android](), [Code](), [Framework](), [configuration](), [Google](), [Java]() Tags: [abstract-class](), [android](), [android-framework](), [code](), [configuration](), [constructor](), [evolution](), [java](), [screen](), [state](), [technical](), [viewmodel]() ### AI overview This technical tutorial examines how Android ViewModel works internally and how it helps preserve screen state across configuration changes. It explains that ViewModel itself is a simple abstract class and that state retention results from processes within the Android framework, with correct initialization and factories required for dependencies. ### Source excerpt Android ViewModel. How it works. Hello everybody. This post will be about popular solution from Google for Android developers -- ViewModel (if you are not familiar with it yet -- get started from official documentation). The main goal of article -- show you how viewModel works, how this tool helps us to save state of our screens. First of all it is better to note that viewModel -- is just java code inside Android framework and there is no any magic... almost. This mechanism was improved something about three times from its origin (2017) till the present day. Let's take a look at "Evolution of anatomy". WARNING! This article contains a lot of technical content and internals of Android framework. And please pay attention -- all demonstrated code you can find in your Android Framework using middle-click or ctrl + left-click. There is no any of self-made code -- all is inside Android framework. Attention again -- most of code will be provided in shortened form. Only necessary details. Full versions you can find in Android Framework source codes straight inside your IDE. ViewModel 2017 Honestly, this part (I mean exactly ViewModel's version of 2017) can be unnecessary, because Medium has several articles, that describes viewModel saving state mechanism in first version. I like this one. But I suggest you more code than there. First of all let's take a look at ViewModel class itself. According to official documentation: The ViewModel class allows data to survive configuration changes such as screen rotations. It can lead to research this class. https://medium.com/media/3966f6a014283670bd0d0430100902cd/href It is just simple abstract class. Without any secrets. With one empty method. Can documentation be wrong (or obsolete) so long time? This question is not so obvious. From one side, if you will create your child viewModel and initialize it using constructor, in this case saving states mechanism will not work. But if you are doing everything in the right way (using special initial ## How lambdas work in Kotlin. setOnClickListener transformation (KAD 18) DevFeed: [How lambdas work in Kotlin. setOnClickListener transformation (KAD 18)]() Original publisher: [Read original article]() Published: 2017-03-28T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Kotlin](), [Android](), [Code](), [ui](), [Framework]() Tags: [android](), [android-framework](), [examples](), [how-to](), [implementation](), [kotlin](), [transformation](), [ui-components]() ### AI overview A tutorial explaining how Kotlin lambdas simplify single-method Java interfaces, with examples focused on Android's setOnClickListener and view handling. It covers anonymous-class transformations, trailing lambdas, omitted parameters, the it keyword, and Kotlin DSL-style code. ### Source excerpt Everything Android, Kotlin and other random topics ## Extension functions in Kotlin: Extend the Android Framework (KAD 08) DevFeed: [Extension functions in Kotlin: Extend the Android Framework (KAD 08)]() Original publisher: [Read original article]() Published: 2017-01-11T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Kotlin](), [Extension](), [Android](), [Code](), [Framework](), [Library]() Tags: [android](), [android-framework](), [code](), [examples](), [extension](), [extension-function](), [framework](), [how-to](), [kotlin](), [library](), [picasso]() ### AI overview A tutorial explaining Kotlin extension functions and extension properties, with Android examples for views, Toasts, adapter view inflation, and Picasso image loading. It describes how extensions add functionality to existing classes without modifying their code and notes that extension properties cannot store state. ### Source excerpt Everything Android, Kotlin and other random topics ## Kotlin integrations with Android SDK (KAD 05) DevFeed: [Kotlin integrations with Android SDK (KAD 05)]() Original publisher: [Read original article]() Published: 2016-12-19T00:00:00Z Content type: tutorial Language: en Sources: [Antonio Leiva]() Topics: [Kotlin](), [Android](), [SDK]() Tags: [android](), [android-framework](), [kotlin](), [sdk]() ### AI overview A tutorial explaining how Kotlin integrates with the Android SDK and Java-based Android framework. It covers mapping Java getters and setters to Kotlin properties and converting single-method interfaces into lambdas, while noting that property access still uses the original getters and setters. ### Source excerpt Everything Android, Kotlin and other random topics ## Using Custom Compound Views in Android DevFeed: [Using Custom Compound Views in Android]() Original publisher: [Read original article]() Published: 2014-05-14T07:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Android](), [Code](), [test]() Tags: [android](), [android-framework](), [code](), [components](), [test]() ### AI overview This tutorial explains how to create reusable custom compound views in Android. It demonstrates encapsulating a variable number of EditText fields in a custom view instead of placing the interaction logic directly in a Fragment, improving reuse and testability. ### Source excerpt On a recent client app, I ran into a situation where I needed an arbitrary number of EditText fields based on a selected value, where the user could enter people's information. My initial thought was to put this logic in my Fragment, just adding EditTexts to a LinearLayout container as the selected value changes, but that bloated my Fragment, and didn't allow for much reuse. This was a perfect opportunity to encapsulate this interaction functionality in a custom view, which would be reusable throughout the app (required in two places so far), and would allow me to easily test the encapsulated functionality.