# android-development Published articles for android-development. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Starting Android at Khan Academy DevFeed: [Starting Android at Khan Academy]() Original publisher: [Read original article]() Author: Khan Academy Published: 2016-02-29T23:00:00Z Content type: article Language: en Sources: [Khan Academy]() Topics: [Android](), [android-development](), [Development](), [Library](), [modules](), [ci](), [Mocking]() Tags: [android](), [android-development](), [development](), [engineering](), [libraries](), [mobile](), [mocking](), [module](), [modules](), [news](), [open-source](), [picasso](), [play-store](), [pre-commit](), [retrofit](), [test](), [tests]() ### AI overview Khan Academy describes its first Android app, launched in August 2015, and the engineering practices used to build it. The team adopted established Android and open-source libraries, separated Android-independent core code from the app module, and used fast JVM tests and continuous integration. ### Source excerpt By Ben Komalo The journey of a thousand miles... In March, 2015--almost 1 year ago to the day--we ... Read more ## About DevFeed: [About]() Original publisher: [Read original article]() Published: 2026-09-15T02:35:35.573025Z Content type: article Language: en Sources: [Android Essence]() Topics: [Development](), [Android](), [Programming](), [GitHub]() Tags: [android-development](), [community](), [development](), [github](), [navigation-drawer](), [programming](), [recyclerview]() ### AI overview Android Essence is an introductory Android development resource focused on making programming concepts understandable to learners of all skill levels. It emphasizes core programming fundamentals and accepts requests for additional topics through GitHub issues. ### Source excerpt About Android Essence Android Essence was first launched on September 2, 2015 by Adam McNeilly. It started off with Adam just wanting to share everything he'd learned about Android development with the community. You can find all sorts of historical context from these posts, like understanding a RecyclerView vs ListView, or even working with a navigation drawer (what a throwback). The problem is that there wasn't always a rhyme or reason to the posts. ## Kotlin 2.4.20 Collection Checks and Experimental Context-Sensitive Resolution DevFeed: [Kotlin 2.4.20 Collection Checks and Experimental Context-Sensitive Resolution]() Original publisher: [Read original article]() Author: Andrii Dubovyk Published: 2026-09-14T06:32:51Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Kotlin](), [Compiler](), [Code]() Tags: [android](), [android-development](), [collections](), [compiler](), [experimental](), [features](), [kotlin](), [list](), [mobile-app-development](), [syntax](), [technology]() ### AI overview The article explains two Kotlin features: allDistinctBy and allEqualBy in Kotlin 2.4.20 for checking collection values, and experimental context-sensitive resolution introduced in Kotlin 2.2 to reduce repetition when the expected type is known. ### Source excerpt Kotlin 2.4.20 gives your collections opinions, and 2.2's compiler finally learns to read the room Some Kotlin features get a lot of attention when they arrive. Others are much less noticeable, but still make everyday code a little easier to write. Two examples of the latter are allDistinctBy/ allEqualBy in Kotlin 2.4.20 and context-sensitive resolution, which was introduced experimentally in Kotlin 2.2. allDistinctBy/ allEqualBy: A Simpler Way to Check Collections For years, checking whether all values in a collection were unique often looked something like this: val users = listOf( User(name = "A", age = 20), User(name = "B", age = 25), User(name = "C", age = 30) ) users.map { it.age }.distinct().size == users.size // true It works, but it creates another list, removes duplicates, counts the result, and then compares the sizes just to get a Boolean answer. Kotlin 2.4.20 adds a more direct way to express the same check: users.allDistinctBy { it.age } // true users.allEqualBy { it.age } // false allDistinctBy returns false as soon as it finds a duplicate, so it doesn't need to process the entire collection or create a separate Set. allEqualBy does the opposite: it checks whether all elements produce the same value when passed through the selector. Both functions work with Iterable, Sequence, and arrays. They use structural equality. For floating-point values, they follow Double.equals semantics, so NaN is considered equal to NaN, while -0.0 is different from 0.0. They're still @ExperimentalStdlibApi, so you'll need to opt in before using them in production code. The underlying allDistinct() and allEqual() requests have also been around in YouTrack for quite a while, which makes their appearance in the standard library feel long overdue. Context-Sensitive Resolution: Less Repetition in when The second feature is more about syntax. When the compiler already knows the type you're working with, you can sometimes leave out the type qualifier. Before: enum class Problem { ## On-Device AI Series (Part 5): LiteRT-LM DevFeed: [On-Device AI Series (Part 5): LiteRT-LM]() Original publisher: [Read original article]() Author: Oğuzhan Aslan Published: 2026-09-14T05:59:12Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [LiteRT](), [On-device AI](), [Large Language Model](), [Inference](), [Streaming](), [GPU](), [LLM evaluation / benchmarking](), [PyTorch]() Tags: [ai](), [android](), [android-development](), [benchmarking](), [gpu](), [inference](), [litert](), [llama](), [llm](), [multimodal](), [on-device](), [on-device-ai](), [programming](), [pytorch](), [qwen](), [software-development](), [streaming]() ### AI overview This tutorial explains LiteRT-LM for running large language models on-device. It covers the Engine/Session API, streaming output, system prompts, tool calling, multimodal inputs, thinking mode, and CPU-versus-GPU benchmarking. The article also discusses tradeoffs involving privacy, network independence, latency, memory, sampling configuration, and model capability compared with cloud APIs. ### Source excerpt Put your phone in airplane mode. Open the app, type a question, and watch the answer arrive one token at a time -- no spinner waiting on a network round-trip, no API key, no per-token bill, and nothing you typed ever leaving the device. LiteRT-LM removes the genuinely hard parts of running an LLM on-device -- KV-cache management, token streaming, backend selection -- but it doesn't remove your job so much as relocate it. What's left on your plate is a short, specific list: sizing a combined input+output token budget, owning your own sampling defaults, hand-building system prompts and tool calling out of raw text, and one native-library collision that presents as a SIGSEGV rather than a build error. Know those going in and the API itself is a clean three-step pattern. We'll get there in that order: Why you'd choose this runtime and what it costs you versus the cloud. The Engine/Session model you need to read the code at all. Real implementation samples -- streaming, system prompts and tool calling, multimodal inputs, thinking mode, and CPU-vs-GPU benchmarking. The anti-patterns to avoid. A developer-friendliness rating on the same rubric as Parts 1-4. Why Use LiteRT-LM? You reach for LiteRT-LM instead of hand-rolling generation on top of raw LiteRT when: You need multi-turn conversation, not single-shot inference -- session state and KV-cache bookkeeping are handled for you, and resetting a conversation is a session swap, not a model reload. You need streaming output -- token-by-token delivery for a responsive chat UI, instead of a blocking call that returns everything at once. You're choosing between CPU and GPU per device -- the explicit backend parameter turns that into a runtime decision instead of a build-time guess. You want a pre-converted model without doing your own PyTorch-to-LiteRT conversion work -- the Model Zoo covers Gemma, Qwen, Llama, and more out of the box. You're willing to own sampling -- the engine won't pick sane decoding defaults for you; that's on the ## Android Weekly Issue #744 DevFeed: [Android Weekly Issue #744]() Original publisher: [Read original article]() Published: 2026-09-13T16:28:25Z Content type: article Language: en Sources: [Android Weekly]() Topics: [Android](), [Development](), [Compose](), [Artificial Intelligence](), [Rive animation]() Tags: [android](), [android-development](), [compose](), [developers](), [lottie](), [net-11-preview-7](), [offline-speech-recognition](), [rive](), [speech](), [tutorials]() ### AI overview Android Weekly Issue #744 is a developer digest covering Android architecture and AI, annotation-based DSL APIs, animated paywalls, offline speech recognition in keyboards, Compose dialog blurring, and structural hot reload across Android, iOS, and desktop. ### Source excerpt Articles & Tutorials Sponsored Pushwoosh launches a new Push-only plan Stop overpaying for push notifications. Get powerful push infrastructure for $7 per 1,000 MAU, with high-speed delivery, 99.9% push-to-gateway delivery, migration support, and a 24-month price lock. Calculate your savings. Android's AI Era: Hype vs. Architecture Thomas Künneth examines Android's AppFunctions architecture and agent distribution claims behind Google's "intelligent system" framing. Two Racing Lines: Annotations and the DSL in NetFlow 0.7.0 KMP Bits explains adding an annotation-based API layer atop NetFlow's DSL, keeping compile-time-checked mapping and paging support intact. Sponsored How many app issues fell off your radar this week? Mobile teams deal with a firehose of incoming issues: regressions from QA, beta feedback, Play Store reviews, crashes, etc. AI code makes managing this even harder. Triage by Runway pulls every issue into one inbox, de-dupes, assigns, and tracks fixes so nothing is missed. See how it works. Adding Rive and Lottie Animations to Android Paywalls Jaewoong Eum explains building custom Rive and Lottie animated components for RevenueCat's server-driven Android paywalls. I Put Speech Recognition Inside an Android Keyboard. Here's What Broke. Farhad Ranjbar explores the architecture challenges of building an offline speech-recognition engine inside an Android keyboard. How to blur what's behind a Compose dialog, down to API 23 Timofey Krestyanov explains blurring content behind a Compose dialog across window boundaries, down to API 23. Compose HotSwan 2.0.0: The Future of Hot Reload on Android, iOS, and Desktop Jaewoong Eum introduces Compose HotSwan 2.0's own interpreter engine, enabling structural hot reload across Android, iOS, and Desktop. Place a sponsored post Advertise to more than 80k Android developers! Advertise your Android development related service or product! We reach out to more than 80k Android developers around the world, every week, through ## Kotlin Explicit Backing Fields: Encapsulation Tradeoffs and Downcasting Risks DevFeed: [Kotlin Explicit Backing Fields: Encapsulation Tradeoffs and Downcasting Risks]() Original publisher: [Read original article]() Author: Ehab Elwan Published: 2026-09-13T05:31:32Z Content type: opinion Language: en Sources: [ProAndroidDev - Medium]() Topics: [Kotlin](), [Code](), [Jetpack Compose]() Tags: [android](), [android-development](), [architecture](), [article](), [clean-code](), [code](), [compiler](), [kotlin](), [memory](), [software-architecture](), [stateflow]() ### AI overview This article compares Kotlin's traditional private mutable property plus public read-only wrapper with explicit backing fields. It explains that explicit backing fields can avoid an extra wrapper allocation, but because the underlying object remains mutable, an external downcast may bypass the intended read-only restriction and mutate internal state. ### Source excerpt Why eliminating the double-property boilerplate changes how we protect our architecture Image generated by AIDisclosure: This article was drafted by me and refined with the help of AI tools. If you have written Kotlin in the last few years, you are intimately familiar with the double-property boilerplate. Whether in Android ViewModels or general state holders, maintaining a private mutable property alongside a public read-only property is a chore we have all accepted in the name of strict encapsulation to prevent our internal state from being hijacked by outside classes. It makes the code significantly cleaner (and slightly more memory efficient). However, it fundamentally changes how we protect our state, moving from a physical object boundary to a simple type restriction. Let's look at the tradeoff. The Old Way: Wrapper Protection For years, the standard approach to encapsulating state has looked like this: class OldViewModel { // 1. The private mutable state private val _uiState = MutableStateFlow(UiState()) // 2. The public read-only state val uiState: StateFlow = _uiState.asStateFlow() } This is tedious to write, but it provides a strict architectural guarantee. When you call .asStateFlow(), Kotlin does not just change the type; it creates a brand new wrapper object in memory (ReadonlyStateFlow). While this physical barrier is fantastic for safety, it does mean you are incurring a minor memory allocation overhead by creating a secondary wrapper object for every exposed state. The New Way: Upcasting Explicit Backing Fields allow you to merge these two properties into one concise declaration, bypassing that extra memory allocation entirely: class NewViewModel { val uiState: StateFlow field = MutableStateFlow(UiState()) } Inside your class, the Kotlin compiler smart-casts the field so you can mutate it internally. Outside the class, the compiler restricts callers to the read-only StateFlow interface. It looks incredibly clean and saves an allocat ## The Android Startup Pattern: A Lifecycle-Aware, Multi-Module Approach DevFeed: [The Android Startup Pattern: A Lifecycle-Aware, Multi-Module Approach]() Original publisher: [Read original article]() Author: Ehab Elwan Published: 2026-09-13T05:31:09Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Android](), [modules](), [Jetpack](), [Framework]() Tags: [android](), [android-development](), [app-startup](), [architecture](), [framework](), [jetpack](), [kotlin](), [mobile-architecture](), [module](), [privacy](), [software-architecture]() ### AI overview This tutorial presents a lifecycle-aware, dependency-injection-driven startup pattern for modular Android applications. It contrasts a centralized startup anti-pattern with Jetpack App Startup and discusses process lifecycles, testability, and delaying tracking SDK initialization until privacy consent is evaluated. ### Source excerpt A Clean, DI-Driven Architecture for Managing Cold Starts, Background Wakeups, and Privacy Compliance in Modern Android Apps Image generated by AIDisclosure: This article was drafted by me and refined with the help of AI tools. Every growing Android project eventually spawns a two-headed "God Class." On one side, your Application class becomes a dumping ground for global infrastructure--third-party SDKs, crash reporters, and tracking tools. On the other side, your main entry point (typically the MainViewModel) gets choked with UI-blocking startup logic. It usually looks something like this: The Anti-Pattern: The Two-Headed God Class class MyApplication : Application() { override fun onCreate() { super.onCreate() // The framework dumping ground CrashReportingSDK.getInstance().setCollectionEnabled(true) HeavyUiSDK.initialize(context = this, ...) AnalyticsSDK.initialize(this, "API_KEY") // ... 50 more lines of spaghetti } }class MainViewModel : ViewModel() { init { // The UI-blocking dumping ground updateRemoteConfigs() checkUserSessionToken() processPendingDeepLinks() prefetchHomeFeedData() // ... UI cannot render until this finishes } } Splitting initialization across these two files creates major problems: It breaks the Single Responsibility Principle: The app's entry points are forced to orchestrate the inner workings of every single feature, tightly coupling your modules. It ignores process lifecycles: Application tasks run indiscriminately on every silent background wakeup, while MainViewModel tasks fail to re-trigger when the app returns to the foreground. It destroys testability: Hardcoding SDK initializations directly into your entry points makes it incredibly difficult to write isolated unit tests without complicated mocking setups. It complicates privacy compliance: A centralized dumping ground makes it extremely difficult to dynamically suspend tracking SDKs until user consent under global privacy regulations (such as GDPR, CCPA, and CPRA) is explicitly grant ## Setup On Device Gemma 4 Android Development on Emulator DevFeed: [Setup On Device Gemma 4 Android Development on Emulator]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-11T14:27:55Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [gemma4](), [Android](), [Emulator](), [android-development]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [artificial-intelligence](), [emulator](), [gemma](), [gemma-4](), [google](), [mobile-app-development](), [on-device]() ### AI overview A tutorial explaining how to set up and run the Gemma 4 large language model locally on an Android Emulator, including downloading and testing the Google AI Edge Gallery sample app. It notes that emulator storage and memory may affect model use. ### Source excerpt Create Android Project with Downloadable Android On Device Gemma 4 Model Continue reading on Mobile App Development Publication " ## Android Studio Quail Using On Device Gemma 4 Experience DevFeed: [Android Studio Quail Using On Device Gemma 4 Experience]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-09-09T11:28:45Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Android Studio](), [gemma4](), [Large Language Model](), [Development]() Tags: [agent](), [android](), [android-development](), [android-studio](), [development](), [gemma](), [gemma-4](), [llm](), [local](), [memory](), [mobile-app-development](), [on-device]() ### AI overview This article describes using the on-device Gemma 4 model in Android Studio Quail for Android development. It outlines selecting the local model option, choosing Gemma in Model Providers, and downloading a model, while noting the need for a fast machine with substantial memory. ### Source excerpt How's Android Studio Quail support for On-Device LLM Model Doing? Continue reading on Mobile App Development Publication " ## From Permissions to Sessions: Rethinking Location Access in Android 17 DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-09-09T01:15:51Z Content type: tutorial Language: en Sources: [ProAndroidDev - Medium]() Topics: [Android](), [Jetpack Compose](), [android-development](), [implementation](), [ui]() Tags: [android](), [android-development](), [android-permissions](), [android17](), [androiddev](), [compose](), [development](), [feature](), [how-to](), [implementation](), [jetpack-compose](), [permission]() ### AI overview A tutorial on implementing Android 17's system-rendered Location Button in Jetpack Compose. The button uses the USE_LOCATION_BUTTON permission and grants precise location for the current session, with local rendering fallback on older Android versions or when remote rendering fails. ### Source excerpt Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th ## From Permissions to Sessions: Rethinking Location Access in Android 17 DevFeed: [From Permissions to Sessions: Rethinking Location Access in Android 17]() Original publisher: [Read original article]() Author: Nav Singh Published: 2026-09-03T18:18:32Z Content type: tutorial Language: en Sources: [Stories by Nav Singh 🇨🇦 on Medium]() Topics: [Android](), [Jetpack Compose](), [Mobile](), [ui]() Tags: [android](), [android-development](), [android-permissions](), [android17](), [androiddev](), [branding](), [consent](), [how-to](), [implementation](), [jetpack](), [jetpack-compose](), [layout](), [permissions]() ### AI overview A tutorial on implementing Android 17's system-rendered Location Button in Jetpack Compose applications. It explains session-only precise location access, the USE_LOCATION_BUTTON permission, the required Jetpack library, fallback rendering, and UI customization. ### Source excerpt Image generated using Gemini In this article, we will learn how to implement the new 📍Location button introduced in Android 17 in Jetpack Compose-based Android applications. Android 17 adds a system-rendered 📍Location Button that we can drop into the layout via a Jetpack library, and tapping it gives the app precise location for that session only, gated by a new USE_LOCATION_BUTTON permission. What the feature is Android now exposes a system-owned, standard location button that we can embed in our UI instead of designing a custom control. When the user taps it, the system handles the permission flow, then grants the app precise location for the current session only, rather than long-lived access. How it changes permissions Instead of immediately requesting ACCESS_FINE_LOCATION (and maybe ACCESS_COARSE_LOCATION) at runtime, we declare the new USE_LOCATION_BUTTON permission to host the button. Developer benefits Less custom permission boilerplate: We lean on system UX and the Jetpack library for the hardest parts of location consent. [versions] locationbuttonCompose = "1.0.0-alpha01" [libraries] androidx-locationbutton-compose = { group = "androidx.core.locationbutton", name = "locationbutton-compose", version.ref = "locationbuttonCompose" } Higher trust and clarity for users: the control looks and behaves consistently across apps, and session-only precise access is easier to understand than broader access. Implementation As we all know, Android development is now Compose-first, so we will implement it using the LocationButton composable provided by th ## Animating between numbers in Jetpack Compose DevFeed: [Animating between numbers in Jetpack Compose]() Original publisher: [Read original article]() Author: hitherejoe Published: 2026-09-02T12:37:43Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Jetpack Compose](), [ui](), [API](), [Tooling]() Tags: [android](), [android-app-development](), [android-apps](), [android-development](), [androiddev](), [animation](), [api](), [app-development](), [apps](), [jetpack-compose](), [jetpackcompose](), [mobile-app-development](), [ui]() ### AI overview This tutorial explains how to animate changing numerical portfolio values in Jetpack Compose. It uses animateFloatAsState with a target value and a tween animation configured with a 500ms duration and FastOutSlowInEasing. ### Source excerpt When it comes to displaying portfolio data inside of Sleevd, users can change the selected filters which will adjust the portfolio values based on that selection. Alongside the main graph, we show the total portfolio value along with some small statistics for collection counts. When the user moves between the filter options, the values of... Continue reading -> ## Proficient Android AI training program addresses AI-agent workflows for Android teams DevFeed: [Proficient Android AI training program addresses AI-agent workflows for Android teams]() Original publisher: [Read original article]() Author: Jorge Castillo Published: 2026-08-25T07:21:15Z Content type: opinion Language: en Sources: [Effective Android]() Topics: [Android](), [android-development](), [AI-assisted coding](), [AI Agent](), [Development](), [Mobile]() Tags: [ai-agents](), [ai-coding-agents](), [android](), [android-development](), [productivity](), [workflows]() ### AI overview The author describes common problems Android teams encounter when using AI coding agents, including repeated context, nondeterministic output, poorly reviewed code, generic prompts, fragile tests, and oversized pull requests. The article announces Proficient Android AI, a practical training program focused on improving AI-agent workflows for Android engineers and teams. ### Source excerpt Proficient Android AI teaches Android engineers how to get ahead with AI agents now: better output, fewer wasted tokens, more deterministic results, and workflows built for real Android teams. ## Build intelligent Android apps: Introduction to Jetpacker DevFeed: [Build intelligent Android apps: Introduction to Jetpacker]() Original publisher: [Read original article]() Author: Android Developers (noreply@blogger.com) Published: 2026-07-21T13:00:00Z Content type: tutorial Language: en Sources: [Android Developers Blog]() Topics: [android-development](), [Mobile](), [On-device AI](), [Inference](), [genai](), [Open Source](), [App](), [ui](), [Google]() Tags: [android](), [android-development](), [apps](), [genai](), [google](), [inference](), [on-device](), [open-source](), [ui]() ### AI overview This introduction to a technical blog series presents Jetpacker, an open-source Android showcase app built for Google I/O. It outlines choices involving on-device, cloud, and hybrid inference, Android system integration, and agentic flows, with later posts promising implementation guidance and code examples. ### Source excerpt Posted by Jolanda Verhoef, Senior Developer Relations Engineer, Android Developer Relations Building GenAI features in your app usually means navigating through various models, APIs and architecture choices: Execution location: Where does your model run? On device, in the cloud, or both? Complexity: How complex is your setup? Are you doing a single inference call or do you need a more agentic flow? In-app or Android System: Should your feature be built into your Android app or does it fit better as an Android system integration? In this blog post series we'll navigate these choices with you. We will take you along on a journey, starting with a basic mobile app and transforming it into a personalized, intelligent, and agentic experience. Jetpacker: a demo travel app Jetpacker is a technical showcase app that our team built from the ground up for this year's Google I/O (built using Antigravity). At its core, Jetpacker helps users plan, explore, and enjoy their next big adventure. It shows an overview of your trips, the itinerary of each trip, and details of each event on that trip. Of course following all best practices of Android development, including a beautifully expressive Material UI design. And best of all? It's fully open source! Today we are publishing a series of technical blog posts diving deep into each of these features. We'll provide detailed implementation steps, code snippets, and architectural insights to help you build your own intelligent Android applications. On-device intelligence On-device features in Jetpacker: Summarizing trip itineraries, managing expenses, and voice notes Using an on-device model comes with no additional cloud inference costs, means you don't have to worry about internet connectivity, and lets users be confident that private information will be processed locally, on the device, without any of their data being sent to the cloud. In Jetpacker, we chose on-device inference for three of our features: The trip overview feature tra ## Practical Kotlin Multiplatform: Setting up the Kotlin Multiplatform Networking Module with Ktor DevFeed: [Practical Kotlin Multiplatform: Setting up the Kotlin Multiplatform Networking Module with Ktor]() Original publisher: [Read original article]() Author: hitherejoe Published: 2026-07-10T16:16:31Z Content type: tutorial Language: en Sources: [Joe Birch]() Topics: [Kotlin Multiplatform](), [Kotlin](), [Ktor](), [networking](), [REST API](), [Authentication](), [Firebase](), [Gradle](), [implementation](), [Android](), [iOS]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [app-development](), [authentication](), [firebase](), [gradle](), [implementation](), [ios](), [jetpack-compose](), [kotlin](), [kotlin-multiplatform](), [ktor](), [library](), [mobile-app-development](), [module](), [networking](), [rest-api]() ### AI overview A tutorial series installment that sets up a Kotlin Multiplatform networking module with Ktor for shared Android and iOS code. It describes building a portable Firebase Authentication and Firestore REST API layer without relying on platform-specific SDKs. ### Source excerpt This post is part one of a series adapted from Practical KMP, my book on building production Kotlin Multiplatform apps for Android and iOS. Part 1: Creating the Kotlin Multiplatform Module In this part of the book, we'll build the complete authentication remote store, defining a repository that handles every operation our app needs for... Continue reading -> ## Google IO 26: Gemini, Big Rocks, Opportunities for Android DevFeed: [Google IO 26: Gemini, Big Rocks, Opportunities for Android]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-07-05T09:06:38Z Content type: article Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Android](), [Google](), [Artificial Intelligence](), [AI Models](), [android-development](), [AI tools for developers]() Tags: [ai](), [ai-models](), [ai-tools-for-developers](), [android](), [android-app-development](), [android-development](), [androiddev](), [gemini](), [google](), [google-io](), [mobile](), [mobile-app-development]() ### AI overview This article reviews Google I/O 26 with a focus on Gemini models, developer tools, the Android ecosystem, Android 17, and opportunities involving UI, performance, and AI. ### Source excerpt In the AI Age, Google continue to thrive in its mobile ecosystem Continue reading on Mobile App Development Publication " ## Как мы мигрируем навигацию на Compose в Android-приложениях с 400+ экранами DevFeed: [Как мы мигрируем навигацию на Compose в Android-приложениях с 400+ экранами]() Original publisher: [Read original article]() Author: horseunnamed (hh.ru) Published: 2026-06-09T08:00:40Z Content type: article Language: ru Sources: [HeadHunter RU]() Topics: [Compose](), [Android](), [ui]() Tags: [android](), [android-development](), [compose](), [hh-ru](), [migration](), [mobile-development](), [modo](), [navigation](), [refactoring](), [tag-08a48a9394c3](), [tag-ae979152fd5d](), [tag-f538878e20ff](), [ui](), [vj]() ### AI overview An Android tech lead at hh.ru describes the ongoing migration of two Android applications from Fragment-based navigation toward a Compose-first approach. The article explains the scale of the migration, the hierarchy of navigation containers, nested navigation flows, and multistack navigation between main application sections. ### Source excerpt Привет, Хабр! Меня зовут Константин Дубинко, я -- Android-техлид в hh.ru. Сейчас мы заканчиваем большой переезд навигации в двух Android-приложениях -- для соискателей и работодателей. В этой статье я покажу, как у нас там устроена навигация, почему мы решили отказаться от Fragment-навигации и как превратили хаотичную миграцию с "островками" новой архитектуры в управляемый процесс с метриками и понятным планом работ. Заодно расскажу, какие решения сработали, какие -- нет, и что я сделал бы иначе, если бы начинал заново. Читать далее ## Android 17: 15 Important Changes to Keep Your App Working DevFeed: [Android 17: 15 Important Changes to Keep Your App Working]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-05-24T14:13:07Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Android](), [Development](), [android-development](), [Mobile]() Tags: [android](), [android-app-development](), [android-development](), [app-development](), [coding](), [development](), [mobile](), [mobile-app-development](), [performance](), [software-development]() ### AI overview This article outlines 15 changes developers should consider when preparing Android apps for Android 17, with emphasis on maintaining compatibility, performance, security, and Play Store compliance. ### Source excerpt Prepare Your App for a More Secure, High Performance, and Android XR Ready Future. Continue reading on Mobile App Development Publication " ## An Android Developer's Journey from Learning to Build Apps to Practicing the Craft DevFeed: [An Android Developer's Journey from Learning to Build Apps to Practicing the Craft]() Original publisher: [Read original article]() Author: Adam McNeilly Published: 2026-05-17T00:00:00Z Content type: opinion Language: en Sources: [Android Essence]() Topics: [Android](), [android-development](), [Java](), [Mobile](), [Programming](), [AdventureX 2026]() Tags: [android](), [android-development](), [app](), [hackathons](), [java](), [learning](), [programming]() ### AI overview The author reflects on learning Android development, beginning with a todo list app and later developing and maintaining applications with practical benefits. The article emphasizes learning from courses, practicing by building, and connecting with other software engineers through hackathons. ### Source excerpt "If you don't learn how to use AI, you're going to be left behind." So leave me behind. I learned to build Android applications in 2014. I was in college taking a Java programming class, when a classmate shared a free online course to learn Android development. The goal was short: build a todo list app with local storage. When I completed the minimum requirements, I unplugged my phone from my laptop and went over to my parents to show them what I built. I often refer to this as my "lightbulb moment". Here in my hands was a real, tangible piece of software that I built and could interact with. It wasn't the first time I programmed something, but it was the first time I had an application on a device that I could carry over and show someone. The app lived in my pocket, always available when I needed it, to help me stay organized and productive. ## How Compose is changing UI development DevFeed: [How Compose is changing UI development]() Original publisher: [Read original article]() Published: 2026-05-11T00:00:00Z Content type: opinion Language: en Sources: [Kt. Academy]() Topics: [Compose](), [Jetpack Compose](), [Android](), [Kotlin](), [Web Development](), [React](), [Vue.js](), [Web](), [wasm]() Tags: [adaptive](), [android](), [android-compose](), [android-development](), [compose](), [desktop](), [frontend-development](), [ios](), [javascript](), [kotlin](), [react](), [screenshot-testing](), [workshop-learning-programming]() ### AI overview This video transcript argues that Compose, a Kotlin-based declarative UI framework, is expanding beyond Android to iOS, desktop, and websites. It highlights Compose's shared tooling, adaptive layouts, previews, screenshot testing, and native animations while acknowledging weaker browser debugging support than traditional web tools. ### Source excerpt How Compose is changing the game in UI development. ## Android Development on Android: A Self-Contained Setup DevFeed: [Android Development on Android: A Self-Contained Setup]() Original publisher: [Read original article]() Published: 2026-04-26T00:00:00Z Content type: tutorial Language: en Sources: [Vasya Drobushkov]() Topics: [Termux](), [android-development](), [Command-line interface](), [Gradle](), [Java](), [Git]() Tags: [android](), [android-development](), [android-studio](), [build](), [cli](), [development](), [git](), [gradle](), [java]() ### AI overview A practical guide to setting up Android development directly on an Android phone with Termux. It covers installing the JDK, Android command-line tools, platform and build tools, Gradle, and a Termux-compatible aapt2 binary, then cloning and assembling a project and authenticating Gemini. ### Source excerpt I use my phone on a daily basis for dozens of various things. This is truly my pocket computer that helps me with many different tasks. Since the first time I had an Android phone until nowadays, the flexibility of the platform has been very astonishing Recently, I've learned about Termux - it is a UNIX terminal running on the phone. Yes, just directly on a mobile phone you have access to git, ssh, curl, and other terminal commands. It is very powerful by itself to be able to connect to a remote server from a phone and do sth, but one thing came to my mind - whether it can be used to work on Android projects ## Android Skills: Expert Instructions for Your AI Agent DevFeed: [Android Skills: Expert Instructions for Your AI Agent]() Original publisher: [Read original article]() Author: blundell Published: 2026-04-24T22:10:46Z Content type: tutorial Language: en Sources: [Blundell]() Topics: [Android skills](), [Agent Skills](), [AI Agent](), [Claude Code](), [Mobile](), [GitHub]() Tags: [agent-skills](), [ai](), [ai-agent](), [android](), [android-development](), [android-skills](), [androiddev](), [claude-code](), [gemini](), [github](), [intermediate](), [reference](), [reference-ai-androiddev-claude-code-gemini](), [skills]() ### AI overview This tutorial explains Google's Android skills repository and the open agent-skills format, then shows how to make the skills available in Claude Code instead of using the repository's default Gemini CLI setup. ### Source excerpt Google just published a set of Android skills a collection of expert, AI-optimised instructions covering the most common and painful Android development workflows. (Upgrading to AGP 9, migrating XML layouts to Compose, wiring up Navigation 3.) AI automated step-by-step procedures grounded in official Android best practices. The GitHub repo defaults to wiring them into Gemini [...] The post Android Skills: Expert Instructions for Your AI Agent first appeared on Blundell. ## A Practical Guide to Paging 3 in Jetpack Compose DevFeed: [A Practical Guide to Paging 3 in Jetpack Compose]() Original publisher: [Read original article]() Author: Elye - A Dev By Grace Published: 2026-04-07T08:16:16Z Content type: tutorial Language: en Sources: [Mobile App Development Publication - Medium]() Topics: [Jetpack Compose](), [Android](), [Kotlin](), [GraphQL](), [API](), [Mobile](), [mobile-app-development](), [App]() Tags: [android](), [android-app-development](), [android-development](), [androiddev](), [api](), [graphql](), [guide](), [how-to](), [jetpack-compose](), [kotlin](), [mobile](), [mobile-app-development](), [programming]() ### AI overview A practical tutorial on using Paging 3 with Jetpack Compose to paginate server data from a GraphQL API in an Android application. It covers the limitations of loading very large lists at once and introduces built-in handling for loading states, retries, scroll-triggered fetching, and empty states. ### Source excerpt How To Elegantly Page Your Server Data on Your Android App Continue reading on Mobile App Development Publication " ## Exploring CompositionLocal API internals in Jetpack Compose DevFeed: [Exploring CompositionLocal API internals in Jetpack Compose]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2026-03-09T05:19:42Z Content type: article Language: en Sources: [Shreyas Patil's Blog]() Topics: [Compose](), [Jetpack Compose](), [API](), [Kotlin](), [Code]() Tags: [android](), [android-development](), [compose](), [data](), [deep-dive](), [implementation](), [internals](), [jetpack](), [jetpack-compose](), [kotlin](), [source]() ### AI overview A deep dive into Jetpack Compose's CompositionLocal API, explaining how values flow implicitly through the composition tree and how the system is implemented with class hierarchies, value holders, persistent maps, and Composer integration. ### Source excerpt Deep dive into the internals of Jetpack Compose's CompositionLocal API. Trace how data flows implicitly through the composition tree under the hood. [Next page]()