I'm currently using Avonni Flow Components 6.4 (04tKY000000xX6C) and things are working great. In light of your partnership announcement, it appears that the path forward is with the 40+ App Builder, Experience Sites and Dynamic Components
package? If so, what is the upgrade process?
Also, what are the major differences between the above package and the 70+ Flow Components package? When should I use one versus the other?
This is a great question, Jack! To clarify, the new package is not a replacement for your current Flow components; instead, it’s a complementary solution
designed for different parts of Salesforce.
Think of it as having two different toolsets for two different jobs:
1. The 70+ Flow Components Package (What you have now)
- Where to use it: Exclusively inside the Salesforce Flow Builder.
- Best for: Guided, multi-step processes and wizards that require moving a user from Screen A to Screen B.
2. The 40+ App Builder & Experience Components Package
- Where to use it: Inside the Lightning App Builder (Record Pages) and Experience Builder (Sites).
- Best for: Enhancing your actual page layouts or building customer portals. These components live directly on the page and don't need to be wrapped in a Flow to work. Use this when you want to add high-performance, reactive components (like timelines or data tables) directly onto an Account page or a public site.
Is there an "Upgrade" process? No upgrade or migration is necessary. Because they serve different purposes, both packages can (and often should) coexist in the same org.
Your existing Flows will continue to work exactly as they do now.
When to use one versus the other?
- Use Flow Components when building a process-driven "wizard."
- Use Dynamic Components to enhance a Record Page or build an Experience Cloud site.
The real power comes when you use both together. For example, you can build a Dynamic Component for a Record Page to display data beautifully, and from that component, launch a Screen Flow
(via a dialog or panel) to handle complex user interactions.
This creates a powerful extension of the no-code solution builder in Salesforce—giving you total flexibility over both the page layout and the business logic.
I hope this helps clear up the path forward!
