Salesforce announced Multi-Framework recently, an open beta that lets developers build native Salesforce apps in React instead of Lightning Web Components. Most of the coverage has focused on what this means for internal dev teams, and fair enough, that's what the beta supports today; but I think the more interesting story is the marketplace. If Salesforce eventually allows React-based apps to be packaged and distributed, the economics of building commercial products on the platform change dramatically.

Quick background for anyone outside the ecosystem. For years, building anything on Salesforce meant learning their proprietary frontend stack. LWC is solid, but it walled off the broader JavaScript world. The React ecosystem, the component libraries, the tooling, the sheer number of developers who already know it, none of that could touch the platform without ugly workarounds. Multi-Framework changes that. You scaffold a project with the Salesforce CLI and what comes out is just a normal React app. Vite, Tailwind, npm, the whole familiar toolchain, with an SDK that handles authentication and gives you GraphQL and Apex access out of the box.

Now play that forward to the AppExchange, recently renamed AgentExchange.
Today the beta is limited to internal apps in sandboxes and scratch orgs. Nothing official yet about managed packages or marketplace distribution. But the direction seems obvious to me, and if Salesforce opens this up to ISVs at general availability, the math on building a commercial Salesforce app changes completely.

Think about what it has taken to ship an AgentExchange product until now. You needed developers fluent in a framework that exists nowhere else, which meant a small hiring pool and a long ramp. Your frontend investment was trapped on the platform. If you had a great product running on the open web, bringing it to Salesforce meant a rebuild, not a port. Plenty of good software never made the trip because the trip wasn't worth it.

A React-native platform lowers that wall to almost nothing. The same team that builds your web product can build your Salesforce edition. Component libraries carry over. And with AI-assisted development tools like Agentforce Vibes generating React apps from plain language prompts, the floor for speed and polish keeps rising. I genuinely believe we'll see marketplace apps in the next couple of years that would not have been possible 24 months ago, built faster and looking better, because the talent pool just went from thousands of LWC specialists to millions of React developers.

Here's why Salesforce should want this too. The AgentExchange has always been their farm system. When an app category gets hot, the top performer tends to get acquired and pulled closer to the core. SteelBrick is the classic case. It was a CPQ app built on the platform, Salesforce bought it in 2015, and it spent the better part of a decade as Salesforce CPQ. Sold as a managed package add-on rather than truly baked into core, sure, but it became the default quoting answer for the whole ecosystem. Vlocity is an even cleaner example. Built on the platform, acquired in 2020, and now it literally is Salesforce Industries.

I see that flywheel daily in my own corner of the ecosystem. Salesforce CPQ is now being retired in favor of Revenue Cloud Advanced, which is rebuilt natively into the platform. That's the full arc, from third-party app to acquisition to add-on to native product. Better marketplace apps feed that cycle. More of them, built faster, by more developers, means a richer pipeline of future acquisitions and future product.

The honest caveats: it's beta, sandbox only, no production deploys, and the ISV story is my speculation until Salesforce says otherwise. But if you're an ISV founder or a product leader who passed on the AppExchange because of the development tax, I'd start paying attention now.

Curious what others in the ecosystem think. Does React support change your appetite for building on the AppExchange?