Dynamic vs. Flow Components
Last updated
Was this helpful?
Last updated
Was this helpful?
Avonni Dynamic Components vs. Components for Flows
Avonni offers two powerful no-code solutions to customize Salesforce UIs. Both build great experiences without code, but they're designed for different places. This guide helps you pick the right one, fast.
Choosing between Avonni Dynamic Components and Avonni Components for Flows primarily depends on where you need to create your custom user interface within Salesforce. Ask yourself this key question:
Scenario: You are using the Lightning App Builder to modify or create custom sections, layouts, or entire interfaces on standard Salesforce pages like App Pages, Record Pages (Account, Contact, custom objects, etc.), or Home Pages.
Your Goal: To build reusable UI elements, custom dashboards, unique record views, interactive data visualizations, or complex layouts that appear as part of the standard Salesforce page, outside of any specific Flow process.
✅ Then Choose:
(Why?) These components are optimized for performance, reusability across multiple pages, and native reactivity directly within the Lightning Page environment.
Scenario: You are using Flow Builder to create a guided, multi-step process, a wizard for data entry, an approval workflow with user input, or any task that involves navigating through different screens within a Flow.
Your Goal: To enhance the visual appearance and interactivity of the screens presented to the user during that Flow.
✅ Then Choose:
(Why?) These components are designed to integrate seamlessly with Flow Builder, leveraging Flow variables and logic within the Flow runtime environment.
In essence
If your work is inside Flow Builder, use Components for Flows. If your work is on a Lightning Page using the App Builder, use Dynamic Components
(Visual Suggestion: Use icons next to each point)
📄 Lightning Page Customization: Build unique App, Record, & Home Pages.
♻️ Reusable: Build once, deploy across many pages.
⚡ Performance: Optimized for fast loading directly on pages.
🔗 Native Reactivity: Components update automatically (no complex formulas!).
🎨 Full Layout & Style Control: Design complex interfaces visually.
📊 Data Visualization: Ideal for dashboards, charts, interactive tables.
(Visual Suggestion: Use icons next to each point)
➡️ Guided Processes: Perfect for multi-step wizards and forms.
📝 Enhance Flow Screens: Make your Flow interactions visually appealing.
🤖 Flow Logic Integration: Works seamlessly with Flow variables and decisions.
✅ Structured Data Input: Great for controlled data entry steps
Environment
Lightning App Builder
Flow Builder
Reusability
✅ High (Across Pages)
➖ Low (Single Flow)
Reactivity
✅ Native / Visual
Formulas / Variables
Performance
⚡ Optimized for Pages
Optimized within Flow
Layout
✅ Full Control
Limited by Flow Screen
You can combine them!
Launch Flows from Pages: Use an Avonni Dynamic Component on a Lightning Page to trigger a Flow (using interactions like "Open Flow Dialog/Panel" or "Execute Flow").
Why? Combine the custom UI and performance of Dynamic Components with the powerful process automation of Flows. Start a guided process from a tailored page layout.
Choose based on WHERE you need the custom UI.
Need to enhance Lightning Pages? Use Dynamic Components.
Need to improve screens inside a Flow? Use Components for Flows