Android-Fat-Aar

Visit Tool

android-fat-aar is a Gradle script that allows developers to merge and embed dependencies within generated Android Archive (AAR) files. It simplifies library distribution by creating a single, self-contained AAR.

Claim this tool

1View

At a glance

Pricing

Open Source

Free tier

Yes

API

Skill level

Technical

About

What is android-fat-aar?

android-fat-aar is a Gradle script designed for Android developers to create "fat" AAR files. This tool enables the merging and embedding of project dependencies directly into the generated AAR, streamlining the distribution of complex libraries. It addresses the challenge of maintaining a modular project structure while publishing a single, comprehensive library. A key benefit is the ability to apply ProGuard to the combined code, which is more effective than processing individual subprojects. While it supports single build types (release out of the box) and offers methods to prevent transitive dependency issues, users should note that manifest placeholders and AIDL file merging are not supported. The project is open-source and available on GitHub.

Best used for

Ideal for developers who need to consolidate multiple Android library dependencies into a single AAR file, simplify library distribution, and ensure efficient ProGuard application across combined code. Especially valuable for maintaining modularity while providing a self-contained library package.

Common actions

merge android dependencies

embed aar files

create fat aar

manage android libraries

optimize android builds

face swappinggithub copilotopen-sourceworkflows"AI Agents"low-code/no-codecollaborationdeepfakeautomated workflow

Capabilities

Key features

Merge dependencies into AAR
Embed subprojects
Prevent transitive dependencies
ProGuard combined code
Gradle script

Target Audience

developer

Integrations

Not yet documented

Pricing & Plans

Open Source

Free

FAQs

What is a "fat AAR" and why would I need one?

A "fat AAR" is an Android Archive file that includes its dependencies embedded within it, rather than listing them as external requirements. Developers use it to publish a single, self-contained library, simplifying dependency management for consumers and allowing for more effective ProGuard optimization across all included code.

Does android-fat-aar support all Android project features?

No, android-fat-aar has some limitations. It does not support manifest placeholders that are expected to be filled by the application, nor does it handle AIDL file merging. Out of the box, it primarily supports a single build type (release).

How do I prevent embedded dependencies from being transitively exposed?

To prevent duplicate class errors, you need to remove embedded dependencies from the generated `pom.xml` file. This ensures that external clients or other projects using your library do not attempt to resolve these dependencies again, as they are already included within your fat AAR.

Trending

Subcategories trending in Coding & Development

Open Source & Models Code Assistants DevOps & Infrastructure No-Code / Low-Code Testing & QA Backend & APIs

Trending

Explore

Browse AI tools by category

Content & Design Productivity & Business Coding & Development AI Agents & Automation Research & Education Wellness & Lifestyle Career Development Marketing & Growth Data & Analytics Customer Support & CX Finance E-commerce