Selection Guide
Choosing the right Avonni Components Package
At Avonni, we provide four component lines designed to supercharge different areas of the Salesforce platform, delivered through three managed packages. Three of the lines are no-code builders for admins. The fourth, LWC Components, is a code library for developers. Same component family, four Salesforce surfaces: pages, flows, sites, and your own code.
The most important thing to know is that these are not "either/or" solutions. Many Avonni power users install more than one package to create a seamless, high-performance user experience. To choose the right package for your current task, start by asking yourself: "Where am I building in Salesforce today?"
Identify Your Needs
Your choice depends on which Salesforce "Builder" environment you are currently using — or whether you are writing code yourself.
I am in the Flow Builder
You need: The 70+ Flow Screen Components package.
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 Experience & Dynamic Components package. One install covers the App Builder, Dynamic, and Experience Site component lines.
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.
I am writing my own Lightning Web Components
You need: The LWC Components package — for your own code.
The Goal: You're a developer writing your own Lightning Web Components, and you want production-ready building blocks instead of starting from scratch. You get 55+ components you reference with
avonni-*tags, exactly like the standardlightning-*ones.Key Strength: The 12 Data Driven components (Data Table, Kanban, Scheduler, Map, Pivot Table and more) can query records themselves, so a full data table is about 30 lines of configuration with no Apex controller behind it.
Choose LWC Components if:
Your team writes custom LWC and keeps rebuilding tables, boards, calendars and maps
You want zero Apex for the data-display layer (query mode handles fetching, search, sort, filter, pagination)
You use AI assistants to write LWC and want them generating against a discoverable component catalog instead of scaffolding black boxes
Install: AppExchange listing · Docs: LWC Components documentation
💡 Pro-Tip: The Hybrid Builder Strategy
Most Avonni power users don't choose just one; they use a Hybrid Approach. They use Dynamic Components 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 (for complex data entry or specific tasks). Developers can join in too: the same avonni-* components power your custom LWC through the LWC Components package. They all work together in the same org!
Component Line Summary
Dynamic Components
Lightning pages (App Builder)
Admins
Experience & Dynamic
Flow Screen Components
Processes (Flow Builder)
Admins
Flow
Experience Cloud Components
External sites (Experience Builder)
Admins
Experience & Dynamic
LWC Components
Your own LWC code
Developers
LWC Components
Component Selection Flowchart
The flowchart below covers the no-code builder packages. If you are writing your own LWC code, go straight to LWC Components.
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.
Custom Code: When your team needs something the builders don't cover, developers build it with the LWC Components package — using the same component family, so the UI stays consistent across the org.
Frequently Asked Questions
Q: Do I need to uninstall my Flow Components to use Dynamic Components? A: No! All Avonni packages are designed to coexist. Installing one does not impact the performance or functionality of the others.
Q: Which package should I start with? A: If your priority is building automated business processes, start with the Flow Package. If your priority is improving the look and feel of your Account/Contact pages or Experience Sites, start with the Experience Package. If your team writes its own Lightning Web Components, start with the LWC Components Package.
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.
Q: I'm a developer. Do I need the no-code packages to use LWC Components?
A: No. LWC Components is a standalone package: install it and reference any avonni-* component directly in your own LWC code. If admins in your org also use the no-code builders, the packages coexist without conflict — and your custom code shares the same component family as their pages, flows, and sites.
Last updated
Was this helpful?