> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/choosing-the-right-components/feature-comparison.md).

# Feature Comparison

The five component lines side by side: who each one is for, where it runs, and what it can do.

## Compare the five component lines

The Avonni suite meets you where you work: the Flow Builder, the Lightning App Builder, Experience Cloud, or your own codebase. Components often share a name (Button, Data Table) while their capabilities differ depending on where they run. This page puts those differences side by side.

If you would rather be walked through the choice, start with the [Selection Guide](/choosing-the-right-components/selection-guide.md). Every line ships in one of three managed packages, and [Installation & Package](/choosing-the-right-components/installation-and-package.md) carries the install links.

{% embed url="<https://www.youtube.com/watch?v=rfw3rIww2LQ>" %}

***

## At a glance

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4>App Builder</h4></td><td>Quick display on Lightning pages, built in the Lightning App Builder.<br><br>Ships in <strong>Avonni Experience Components</strong>.</td><td><a href="https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FBcrppmzFXxWvqYT1WnXM%2Fline-app-builder-kanban.png?alt=media">https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FBcrppmzFXxWvqYT1WnXM%2Fline-app-builder-kanban.png?alt=media</a></td><td><a href="https://docs.avonnicomponents.com/app-builder-components">https://docs.avonnicomponents.com/app-builder-components</a></td></tr><tr><td><h4>Dynamic</h4></td><td>Complex logic on Lightning pages and Experience sites, built in the Component Builder.<br><br>Ships in <strong>Avonni Experience Components</strong>.</td><td><a href="https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2F7ciirtiBZSZoZxj1WEKn%2Fline-dynamic-component-builder.png?alt=media">https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2F7ciirtiBZSZoZxj1WEKn%2Fline-dynamic-component-builder.png?alt=media</a></td><td><a href="https://docs.avonnicomponents.com/dynamic-components">https://docs.avonnicomponents.com/dynamic-components</a></td></tr><tr><td><h4>Flow Screen</h4></td><td>Wizards and guided data collection, built in the Flow Builder.<br><br>Ships in <strong>Avonni Flow Screen Components</strong>.</td><td><a href="https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FKk4YIbOQXrGIIabiKHaq%2Fline-flow-pivot-table.png?alt=media">https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FKk4YIbOQXrGIIabiKHaq%2Fline-flow-pivot-table.png?alt=media</a></td><td><a href="https://docs.avonnicomponents.com/flow">https://docs.avonnicomponents.com/flow</a></td></tr><tr><td><h4>Experience Sites</h4></td><td>Customer and partner portals, built in the Experience Builder.<br><br>Ships in <strong>Avonni Experience Components</strong>.</td><td><a href="https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FqbLestvfe1GEEvAfkHpj%2Fline-experience-sites-map.png?alt=media">https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FqbLestvfe1GEEvAfkHpj%2Fline-experience-sites-map.png?alt=media</a></td><td><a href="https://docs.avonnicomponents.com/experience-cloud">https://docs.avonnicomponents.com/experience-cloud</a></td></tr><tr><td><h4>LWC</h4></td><td>Custom development in your own Lightning Web Components.<br><br>Ships in <strong>Avonni LWC Components</strong>.</td><td><a href="https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FXssXQlk4q2O7Q34eGtkY%2Fline-lwc-template.png?alt=media">https://4064884509-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtAjHpTxL9rEknLdE4DOb%2Fuploads%2FXssXQlk4q2O7Q34eGtkY%2Fline-lwc-template.png?alt=media</a></td><td><a href="https://docs.avonnicomponents.com/lwc-components">https://docs.avonnicomponents.com/lwc-components</a></td></tr></tbody></table>

***

## Who it is for, and where it runs

|                      | App Builder              | Dynamic                  | Flow Screen  | Experience Sites         | LWC                        |
| -------------------- | ------------------------ | ------------------------ | ------------ | ------------------------ | -------------------------- |
| 👥 **Target users**  | Internal                 | Any                      | Internal     | External                 | Any (developer-built)      |
| 🏗️ **Builder tool** | Lightning App Builder    | Lightning and Experience | Flow Builder | Experience Builder       | Your own LWC code          |
| 🎛️ **Setup**        | Fast and easy            | More configuration       | Moderate     | Standard                 | Code (tags and attributes) |
| 💡 **Skill level**   | Beginner to intermediate | Intermediate to advanced | Intermediate | Intermediate to advanced | Developer                  |

## What it can do

|                               | App Builder                           | Dynamic           | Flow Screen                           | Experience Sites | LWC                                  |
| ----------------------------- | ------------------------------------- | ----------------- | ------------------------------------- | ---------------- | ------------------------------------ |
| 🎨 **Branding**               | Salesforce style                      | Custom            | Salesforce style or custom            | Fully branded    | Fully custom (CSS and styling hooks) |
| 🔄 **Multi-step process**     | No                                    | No (display only) | Yes (core feature, with Flow Builder) | No               | Yes (your own logic)                 |
| 📐 **Formulas**               | No                                    | Yes               | Yes (via Flow formulas)               | No               | Yes (via JavaScript)                 |
| 🎭 **Conditional visibility** | Yes (core feature within App Builder) | Yes               | Yes (via Flow logic)                  | Limited          | Yes (via code)                       |
| 🌐 **Guest user support**     | No                                    | Yes               | Yes                                   | Yes              | Yes                                  |

{% hint style="info" %}

#### No line closes another one.&#x20;

A customer portal can run Experience Sites Components for the layout, a Dynamic Component for a reactive dashboard inside it, and a Screen Flow built with Flow Screen Components for the request form. They share styling and behavior, so it reads as one product to the end user.
{% endhint %}

***

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><h4><i class="fa-grid-round-2-plus">:grid-round-2-plus:</i></h4></td><td><h4>Selection Guide</h4></td><td>One question, where are you building today, and a path straight to the line that fits.</td><td><a href="/choosing-the-right-components/selection-guide.md">Selection Guide</a></td></tr><tr><td><h4><i class="fa-arrow-down-to-bracket">:arrow-down-to-bracket:</i></h4></td><td><h4>Installation and Package</h4></td><td>The three packages, their install links, and the four steps that follow an install.</td><td><a href="/choosing-the-right-components/installation-and-package.md">Installation &amp; Package</a></td></tr></tbody></table>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.avonnicomponents.com/choosing-the-right-components/feature-comparison.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
