# Selection Guide ## Choosing the right Avonni Components Package At Avonni, we provide **two distinct packages** designed to supercharge different areas of the Salesforce platform. The most important thing to know is that **these are not "either/or" solutions**. In fact, most Avonni power users install **both** packages to create a seamless, high-performance user experience. To choose the right component for your current task, start by asking yourself: **"Where am I building in Salesforce today?"** *** ## Identify Your Needs Your choice of component depends entirely on which Salesforce "Builder" environment you are currently using. #### I am in the Flow Builder * **You need**: The [**70+ Flow Screen Components package**](https://appexchange.salesforce.com/listingDetail?listingId=a0N4V00000IDsfbUAD\&tab=e). * **The Goal**: You are building a guided process. You need to move a user through a series of steps (Step 1 → Step 2 → Step 3) to collect data or perform complex logic. * **Key Strength**: These components live within your Flow variables, enabling deep integration with your business logic and automation. #### I am in the Lightning App Builder or Experience Builder * **You need**: The [**40+ Experience & Dynamic Components package**](https://appexchange.salesforce.com/appxListingDetail?listingId=2e584bb3-b5e0-415d-9347-d6567158d840\&channel=recommended). * **The Goal**: You are building a page layout. You want to enhance a standard Record Page (Account, Opportunity, etc.), a Home Page, or a public-facing Experience Site. * **Key Strength**: These components are "always-on" and reactive. They live directly on the page layout and don't require a user to "launch" a Flow to see information. {% hint style="success" %} #### 💡 Pro-Tip: The Hybrid Builder Strategy Most Avonni power users don't choose just one; they use a Hybrid Approach. They use [**Dynamic Components**](https://app.gitbook.com/s/ODPvvv7Cx9Z9RECLn3oV/) to build a high-performance, reactive dashboard directly on a Record Page, and then use a "Button" or "Interaction" within that component to launch an [**Avonni Screen Flow**](https://app.gitbook.com/s/1FUd4apB9YHgCEMUFbVb/) (for complex data entry or specific tasks). They work perfectly together in the same org! {% endhint %} *** ## Component Selection Flowchart
*** ## Better Together: The "Extension" Architecture Installing the **Avonni Experience Components package** is not an "upgrade" that replaces your Flow components—it is an **extension** of your no-code capabilities. **Why use both?** * **Modern UI**: Use Dynamic Components to make your standard Salesforce pages look and feel like custom-coded applications. * **Triggered Logic**: Use those beautiful components to trigger your existing Screen Flows. For example, clicking a "Schedule Meeting" button on an Avonni Timeline can launch a Flow that handles the calendar logic. *** ## Frequently Asked Questions **Q: Do I need to uninstall my Flow Components to use Dynamic Components?** \ A: No! Both packages are designed to coexist. Installing one does not impact the performance or functionality of the other. **Q: Which package should I start with?** \ A: If your priority is building automated business processes, start with the [**Flow Package**](https://appexchange.salesforce.com/listingDetail?listingId=a0N4V00000IDsfbUAD\&tab=e). If your priority is improving the look and feel of your Account/Contact pages or Experience Sites, start with the [**Experience Package**](https://appexchange.salesforce.com/appxListingDetail?listingId=2e584bb3-b5e0-415d-9347-d6567158d840\&channel=recommended). **Q: I am using the Flow Components. What is my path forward?** \ A: Continue using this package for all your Flow needs! If you want to start adding components directly to your Lightning Record Pages (outside of a Flow), simply install the **Experience Package** alongside it.