For years, Salesforce developers faced an uncomfortable trade-off. You could build with Lightning Web Components and get full platform access, or you could use the broader React ecosystem and give up platform-native features entirely. There was no middle path.
TDX 2026 changed that. Salesforce announced Multi-Framework, a new runtime that lets developers build native Salesforce apps in React, with Angular and Vue coming next. The platform’s authentication, security, and governance model all remain intact. You no longer have to choose between your framework and your platform.
This is not a minor enhancement. For many teams, it fundamentally reshapes how Salesforce UI development gets staffed, scoped, and delivered.
What Is Salesforce Multi-Framework?
Multi-Framework is a framework-agnostic execution engine running on the Agentforce 360 Platform. It enables developers to build Salesforce apps using React today, with additional frameworks coming in future releases.
Critically, it is not a replacement for Lightning Web Components. Both runtimes coexist on the platform, and your existing LWC investments remain fully intact. Multi-Framework is an additive capability, not a migration mandate.
The feature is currently in open beta for scratch orgs and sandboxes with English as the default language. Production org deployment is not yet available during the beta period.
How It Works Under the Hood
When you scaffold a Multi-Framework React app, you get a pre-configured starter that includes:
- Vite for bundling
- Vitest for testing
- shadcn/ui for components
- Tailwind CSS for styling
- Salesforce Multi-Framework SDK for platform API access
Data access works through the @salesforce/sdk-data package. React components query and mutate Salesforce records via GraphQL, invoke Apex methods directly, and access UI APIs for user context. Authentication is handled automatically through the createDataSDK() utility, so there is no manual token management in application code.
Deploying to your org follows familiar patterns. You build the React app, push via Salesforce CLI, and the app appears in the App Launcher like any other Salesforce app.
React vs LWC: When to Use Which
Multi-Framework introduces a genuine architectural decision that every Salesforce developer team will need to make. Neither option is universally better. The right choice depends on what you are building and who is building it.
Use React when:
- You need to share components across Salesforce and non-Salesforce surfaces
- Your team already has strong React expertise and you want to eliminate the LWC learning curve for new contributors
- You need a specific open-source component library, such as Material UI, Ant Design, or your own internal design system
- The app is complex enough to benefit from the full React ecosystem, including React Query, Zustand, or similar tooling
Use LWC when:
- You want declarative data access through
@wiredecorators and Lightning Data Service - You need the 80+ Salesforce Base Components out of the box
- The app needs drag-and-drop placement in Lightning App Builder (React does not yet support this)
- Your use case benefits from SLDS tokens and built-in accessibility compliance
The comparison table from Salesforce’s official documentation clarifies the differences clearly:
| Capability | React (Multi-Framework) | Lightning Web Components |
|---|---|---|
| Data access | GraphQL, Apex invocations, UI API | @wire decorators, Lightning Data Service |
| Component library | Bring your own (shadcn, MUI, etc.) | 80+ Salesforce Base Components |
| Styling | Tailwind, CSS Modules, CSS-in-JS | SLDS tokens and classes |
| App Builder support | Not yet available | Full drag-and-drop support |
| Cross-platform reuse | Yes, share across Salesforce and external apps | Salesforce-only |
| Ecosystem tooling | npm, Vite, Vitest, React DevTools | Salesforce CLI, LWC Local Dev |
The Talent Ceiling Problem This Solves
This announcement matters beyond pure technical capability. Before Multi-Framework, Salesforce UI work created a hiring bottleneck.
Experienced React developers needed time to learn LWC before contributing meaningfully to Salesforce projects. Teams often had to choose between onboarding cost and delivery speed. For smaller shops and ISVs, that constraint was particularly acute.
Multi-Framework removes that ceiling. React developers can now contribute to Salesforce projects from day one. For ISVs building on the platform, this is arguably the most significant developer experience improvement in years. Component libraries built for non-Salesforce products can now run natively on the platform without heavy re-implementation.
Agentforce Vibes 2.0 and Multi-Framework
Multi-Framework connects directly to Agentforce Vibes 2.0, Salesforce’s AI-assisted development environment. Describe the component you need in natural language, and Vibes generates the React code, GraphQL queries, and Salesforce metadata automatically.
The integration includes a Live Preview capability that renders your React app in real time as you build. Vibes also uses the Einstein Trust Layer to ensure your prompts and responses are never used to train future models, which matters for teams working with sensitive business logic.
Developers who want to try this today can start through the Agentforce Vibes welcome screen by selecting the React App tile and choosing Internal App. Alternatively, the sf template generate ui-bundle CLI command scaffolds a starter app directly.
Beta Limitations to Know Before You Start
Multi-Framework is genuinely ready to explore, but the beta has real constraints worth understanding before you start planning production use cases.
Key limitations at this stage:
- No production org deployment during the beta period
- No Lightning App Builder support for React components yet (planned for GA)
- Micro-frontend support for embedding React components directly into Lightning pages is in closed pilot for Spring 2027
- Some platform APIs are not yet available in the beta runtime
Additionally, beta apps require scratch orgs or sandboxes with English as the default language. Check the official Beta Documentation for the current list of known limitations before scoping work.
What This Means for Your Team Right Now
If you are leading a Salesforce development practice, the most actionable step is experimentation, not migration. Multi-Framework is not asking you to rebuild anything. It is asking whether your next new app might be a better fit for React than LWC.
A few practical steps to take today:
- Spin up a scratch org and run through the official getting started guide
- Identify one non-production project where React’s ecosystem would provide clear value
- Assess your team’s existing React skill level to understand where talent friction currently lives
- Review the 20+ code samples in the Salesforce Multi-Framework Recipes repository on GitHub
The UI layer on Salesforce is entering a period of genuine pluralism. LWC is not going anywhere, React is now a legitimate first-class option, and the Agentforce Experience Layer introduces a third dynamic for agent-assembled interfaces. Understanding when to reach for each tool is becoming a core architectural skill, not just a preference.
Key Takeaways
Salesforce Multi-Framework opens React as a native development path on the Agentforce 360 Platform for the first time. It runs alongside LWC, not in place of it. Data access works through GraphQL and Apex with authentication handled by the SDK. The feature is in open beta now, with production support and App Builder integration coming at GA. Angular and Vue support is on the roadmap.
The decision between React and LWC is no longer philosophical. It is a practical question about component reuse, team skills, ecosystem needs, and platform features. Both are valid answers depending on what you are building.
Read More!
I Presented at Albania Dreamin’ – Built Everything with AI and Didn’t Write a Single Line of Code
Build with React, Run on Salesforce: Introducing Salesforce Multi-Framework
Leave a Reply