One of the five Mini Hacks at Dreamforce this year was a development challenge: build an application with React and run it on Salesforce. The first two articles covered MCP and model selection. This one is about the front end.
For Salesforce front-end development, the familiar progression has been Visualforce, Aura, and LWC. With Salesforce Multi-Framework, we can now develop React applications and deploy them to Salesforce.
At the event, I asked whether to choose React or LWC. The answer was direct: if your team knows React, use React. That made me think the real questions are where the application will run, which platform capabilities it needs, and how comfortably the team can maintain it.
1. How a React application becomes a Salesforce application
The key concept is UIBundle. It brings the front-end application into a Salesforce DX project as metadata. Development uses a front-end toolchain, while deployment follows Salesforce workflows. Multi-Framework overview
The front-end code can be delivered alongside objects, Apex, and permission configuration in the same Salesforce DX project. Choosing React does not require a completely separate application-management approach.
Define the audience early. An internal application for employees differs from an external application for customers or partners in its entry points, templates, and access arrangements.
2. React vs. LWC
My approach is: start with LWC when you need deep integration into standard Lightning pages; seriously consider React for a complete application with clear boundaries and complex interactions.
For example, a small record-page component may depend on Lightning Base Components, page context, and App Builder configuration. LWC is usually a natural fit. Switching frameworks for that local requirement could mean spending extra time reconnecting platform capabilities.
A standalone workspace is a different case. It may have its own navigation and complex interactions, and the team may already have React components and experience. Using that familiar ecosystem can offer more value.
You can compare this distinction with the official documentation’s LWC and Multi-Framework guidance.
3. Embedding in Lightning
If a React application needs to appear inside a Lightning page, Salesforce Microfrontends provides an embedding option. It is currently documented as Beta, using an isolated iframe and a communication channel to connect the application with the surrounding page. Microfrontends embedding guide
Running an application independently and embedding it are distinct usage scenarios. Test sizing, page transitions, and event communication in the actual embedded application.
4. AI can help build pages; the use case still guides the choice
The Mini Hack code was generated through prompts in Agentforce Vibes. That is one reason React interests me: its established ecosystem has many components, tools, and examples that can help us build a prototype quickly.
AI coding tools are now very capable. In my view, implementation effort alone is therefore becoming less decisive when choosing between React and LWC. Understand the strengths and limitations of each, then choose for the business scenario.
What to try now
Start with the official Multi-Framework Quick Start.
For specific data operations, explore the React examples in multiframework-recipes.
Closing thoughts
React gives Salesforce developers another valuable front-end option. My criteria remain the same: clear application boundaries, the required depth of platform integration, and the team’s ability to maintain the solution.
Define the use case first, then choose the framework. Let LWC handle the integrated components it is well suited to, and use React where complete applications and ecosystem reuse offer an advantage.
The event roadmap also described Angular support reaching GA in October 2026 and Vue support expected in spring 2027. Those were roadmap expectations; actual availability depends on the official release and your target environment. The current official overview already lists React and Angular templates.
References
- Salesforce Multi-Framework overview and framework comparison
- Project structure and UIBundle metadata
- React Multi-Framework GA release and beta migration: older tutorials use different Data SDK and application-entry configurations; check them against current documentation.
- Multi-Framework Quick Start
- Microfrontends embedding guide (Beta)
- Official multiframework-recipes examples
- Trailhead: Salesforce Multi-Framework: Quick Look
Based on my Dreamforce 2026 experience and personal assessment. The blog edition restores official documentation, examples, and learning links. Product status reflects documentation checked on October 5, 2026; roadmap dates depend on actual releases. Read the Chinese version.