# aidl Published articles for aidl. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The Future of Android Apps with AppFunctions DevFeed: [The Future of Android Apps with AppFunctions]() Original publisher: [Read original article]() Author: Shreyas Patil Published: 2026-03-30T04:30:00Z Content type: article Language: en Sources: [Shreyas Patil's Blog]() Topics: [Android](), [AI Agent](), [Jetpack](), [SDKs]() Tags: [agentic-ai](), [ai](), [ai-agent](), [ai-agents](), [aidl](), [android](), [android-app-development](), [android-apps](), [app-development](), [gemini](), [jetpack](), [kotlin](), [sdk]() ### AI overview This article explains Android AppFunctions, which let apps expose self-describing data and functionality that AI agents and assistants can discover and execute using natural language. It discusses their optional nature, current device availability, Gemini access, and integration through the Android 16 SDK or Jetpack library. ### Source excerpt Explore the potential of Android AppFunctions for AI agents. Learn how apps can share functionality with intelligent assistants using self-describing functions. ## The legend about AIDL. Part 2. In Action DevFeed: [The legend about AIDL. Part 2. In Action]() Original publisher: [Read original article]() Author: Vladislav Puryev Published: 2021-01-16T14:50:18Z Content type: tutorial Language: en Sources: [Stories by Vladislav Puryev on Medium]() Topics: [Android](), [Process](), [Remote Procedure Call (RPC)](), [Code]() Tags: [aidl](), [android](), [code](), [ipc](), [process](), [rpc]() ### AI overview This tutorial explains how developers can use Android Interface Definition Language (AIDL), including its relationship to RPC and IDL concepts. It focuses on communication between applications and other processes through Android interprocess communication, with code and technical details. ### Source excerpt The legend of AIDL. Part 2. In Action Hello everybody. In previous article you could read about theoretical basics of Interface Definition Language and its main idea. Well, unlike the previous one, this part will contain a lot of code and technical details. Sometimes you will see internal parts of Android system, the parts that most of developers should not worry about in their works. The following material is dedicated to AIDL itself, how developer can use it, how it works and how RPC and IDL concepts are implemented in Android system. I hope you are interested and ready. Let's start! WARNING! The some code will be provided in shortened form. Full versions you can find in your IDE, in AOSP or Android Code Search. Please be careful, cause most of further code can be changed any time by Google developers, that is why some material can be obsolete and partially or completely wrong in the future, but actual for the moment of publication. This series of articles consist of three parts: The legend about AIDL. Part 1. The roots The legend about AIDL. Part 2. In Action (you are here) The legend about AIDL. Part 3. The crucial ingredient AIDL for applications developer I think, that there are just two general situations, when you really need to use Android Interface Definition Language: You have two (or more) applications and you are completely sure, that user will install one "main" application which can provide some functions for others. It means, that one of your applications must be exactly installed on user's device, cause other one (two, four and etc.) wouldn't give user some features without "basic application". It is possible to say, that your "basic application" is a server. You are developer of a new device, based on Android. May be some more usages are exist, but anyway all of them require AIDL power just for one goal -- communication between different processes (process is not always an application). Why so? Well, a lot of parts of Android system and different ap ## The legend about AIDL. Part 1. The roots DevFeed: [The legend about AIDL. Part 1. The roots]() Original publisher: [Read original article]() Author: Vladislav Puryev Published: 2021-01-16T14:45:31Z Content type: tutorial Language: en Sources: [Stories by Vladislav Puryev on Medium]() Topics: [Android](), [distributed-systems](), [Remote Procedure Call (RPC)](), [Processes](), [Programming]() Tags: [aidl](), [android](), [computer-science](), [distributed-systems](), [processes](), [programming](), [remote-procedure-calls](), [rpc]() ### AI overview This first article in a three-part series introduces Android Interface Definition Language (AIDL) and explains its theoretical foundation in Interface Definition Language (IDL). It discusses processes in distributed systems and introduces Remote Procedure Call (RPC) as a way for client applications to invoke server functions without knowing their implementation. The article is theoretical; code examples and Android internals are deferred to later parts. ### Source excerpt The legend of AIDL. Part 1. The roots Hello everybody. I would like to tell you one story about very ancient and not popular character of Android system. Not popular for developers, as they suppose. This is Android Interface Definition Language. In this article I want to tell you about the origin of AIDL, about the base concept -- IDL. Let's get started. WARNING! This article contains theoretical information only. The code examples, internals and actual technical details from Android system will be provided in the next articles. This series of articles consist of three parts: The legend about AIDL. Part 1. The roots (you are here) The legend about AIDL. Part 2. In Action The legend about AIDL. Part 3. The crucial ingredient What is IDL AIDL means Android Interface Definition Language. But before get to know more about platform specific mechanism, it is useful to learn something about its theoretical basis. Let's forget about Android for a while and try to understand what Interface Definition Language is. Well, there are not too many official definitions for this concept, but I like next one (source): Interface definition language -- is a language that describes the interface between client and server process in a distributed system. I suppose it is not very clear. Let's break it down. Independent Communication What is one of the main features of distributed systems? They can interact (even must interact) with many processes. Process is a single complicated concept, which is beyond of this article. Just for now, you should know (if you are not familiar with it) next thing: process is an program (application) at runtime. All of it is quite rough, but enough. More important for distributed systems, that applications can be developed with different programming languages and technologies. And they can be located on different computers. Or they can be on one computer (device), but on distinct and independent virtual machines. Anyway user must have access to programs and res ## Migrating Android Projects to Gradle DevFeed: [Migrating Android Projects to Gradle]() Original publisher: [Read original article]() Published: 2013-07-17T07:00:00Z Content type: tutorial Language: en Sources: [Blogs on Ryan Harter]() Topics: [Gradle](), [Android](), [Dependency management](), [Maven]() Tags: [aidl](), [android](), [build](), [build-system](), [configuration](), [dependency-management](), [gradle](), [maven]() ### AI overview A tutorial on migrating Android projects from Ant to Gradle. It explains Gradle build files, the Android plugin, dependency management through Maven, Android-specific configuration, and how to preserve an existing Ant-style project structure with custom source sets. ### Source excerpt I've been using ant to build my Android projects for as long as I can remember. There are many reasons for this, like build consistency and workstation agnosticism, but you can read this article if you want to check that out. Ant is a good tool, but never offered the flexibility that I would have liked in a project. That's where Gradle steps in. After seeing all of the power of the new Gradle build system, I knew I had to convert Hashnote to Gradle. Google has some great documentation for migrating if you already build with Eclipse, but that doesn't work for me.