> For the complete documentation index, see [llms.txt](https://able.bucca.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://able.bucca.com/core/overview/adapticon.md).

# ε AdaptIcon

Element: Set sizes for display with or without a status badge. Based off of the concept behind [Adaptive Icons](https://developer.android.com/guide/practices/ui_guidelines/icon_design_adaptive) introduced with Android 8.0, Adpicon's display a simple icon inside a variety of shapes.

[Styleguide Link](https://zpl.io/bey1LvW)

* Parent: [AdaptIcon - Bar](/core/overview/adapticon/adapticon-bar.md), ListItem, Multiple others
* Child: [Badge](/core/overview/badge.md), [Icon](/core/overview/icon.md), [AdaptIcon - Shape](/core/overview/adapticon/adapticon-shape.md)

## Properties

### Size & Shape

To account for multiple usecases the design system has established a set sizing standard for certain interface objects, with AdaptIcon being one of those. The size and shape of the AdaptIcon is set within the base level feeder of AdaptIcon - Shape.

<figure><img src="/files/NLBI3aofIQxhf6VPR4Uu" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/rbKq2Qnh3PEOaj5aoNf9" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/a48QqmKxR40QjR6FQdZH" alt=""><figcaption></figcaption></figure>

### Status

Most of the time an adaptIcon is simply shown as a metaphor for something, but it does have the ability to carry a badge as well. There may be situations where a service like email or alerts would be represented on the screen as an AdaptIcon so it will need the capability of sharing additional information in the form of a badge in those situations.

*


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://able.bucca.com/core/overview/adapticon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
