The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Must-read

Salesforce Multi-Framework now supports Angular, microfrontends, and Managed Packages (opens in a new tab)

Readers will learn how to build, embed, and distribute Angular applications directly on the Salesforce Platform using the new Multi-Framework runtime.

Why read this

The article also covers secure cross-app communication, localization, and enterprise authentication requirements.

Multi-Framework runtime capabilities

  • Angular framework support
  • Microfrontend embedding
  • Managed packages
  • Localization and internationalization
  • Multi-factor authentication
  • Multi-Framework Insights
The Winter '27 release introduces key enhancements to the Multi-Framework runtime

Salesforce Multi-Framework is a framework-agnostic runtime that lets developers run modern web apps directly on the Salesforce Platform, inheriting Salesforce authentication, security and governance without a separate hosting stack or manual token handling. After React reached general availability, the Winter ’27 release adds Angular as a second GA framework, with internal, external and basic templates, deployment as a UIBundle metadata type, and the same Data SDK and security model that React apps use. Internal apps run on the Salesforce.app domain, which isolates them from the Lightning runtime and from each other, while platform rules for object-level security, field-level security, sharing and validation continue to apply to data requests and saves.

Microfrontend is now generally available, allowing externally hosted React or Angular apps to be embedded in Lightning Experience, Experience Cloud, the Salesforce mobile app and Mobile Publisher apps without rebuilding them in Lightning Web Components. The lightning-ui-embedding component hosts the app in a sandboxed iframe and provides a two-way channel: hosts pass properties down and embedded apps send custom events back. Managed packages can now distribute non-site, employee-facing Multi-Framework apps together with their supporting metadata such as Permission Sets, Apex and Custom Objects, though site-based apps are not supported. The release also adds locale-aware formatting and localized labels through the Platform SDK and Data SDK, enterprise multi-factor authentication managed by Salesforce, and Multi-Framework Insights in Beta for performance and usage reporting.

The article also describes three ways to build these apps: Agentforce Vibes, now with Angular support and generally available, for code-first development; Builder Central in Beta for natural-language app creation by admins; and Quick Pages in Beta, where business users describe a page in plain language and get a data-driven page that respects the viewer’s security. Salesforce says Vue is the next UI framework planned, along with agentic experiences and Government Cloud support.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?

Must-read

Using Microfrontends and UI Embedding to integrate external web apps into Lightning (opens in a new tab)

You will learn the architecture behind Salesforce Microfrontends, including how the Lightning host and embedded guest application communicate through UI Embedding.

Why read this

The article provides concrete code examples for building both the LWC host and a React-based guest app.

Microfrontend architecture

  • Lightning host
  • UI Embedding
  • Embedded web application
How Salesforce Microfrontends connect external apps to Lightning Experience

The article introduces Salesforce Microfrontends, which use UI Embedding to bring web applications built with React, Angular, Vue, or other standards-based technologies into Lightning pages alongside Lightning Web Components. The architecture has three parts: a Lightning host (a custom LWC that renders the lightning-ui-embedding base component and owns the Salesforce context and data), the embedded guest web application, and UI Embedding as the managed communication layer between them. The guest runs in a sandboxed iframe, which gives the two applications a browser-enforced isolation boundary. The host decides what information to share, and the external origin must be allowed in Salesforce security settings.

The article illustrates this with a ScoreAccount web app that shows an Account’s rating and lets users choose Hot, Warm, or Cold. The host retrieves the record data and passes the state to the guest, which renders it and subscribes to later updates. When the user selects a rating, the guest dispatches a score event that the host handles by updating the Salesforce record, and the host then sends any changed data back down. The article lists the four steps to bring such an app into Lightning: allow the origin, connect the guest to the UI Embedding channel through the Salesforce Platform SDK, create the host LWC, and deploy both sides through their own workflows. It presents the example in React but notes that the approach is not tied to one framework.

The piece argues that Microfrontends suit established web experiences that a team wants to keep on its own framework, infrastructure, and release cycle, such as an existing analytics app or internal search tool, rather than rebuilding them. It positions Microfrontends as complementary to LWC, which remains the native model for Salesforce-specific experiences, and to Salesforce Multi-Framework, where supported frameworks are packaged as UI bundles and hosted on Salesforce. A comparison table shows that externally hosted Microfrontends run on the team’s own infrastructure, while UI bundles are built and deployed through Salesforce workflows. The article gives UI Embedding’s status as GA since September 2026 and UI bundle embedding as in Beta with GA targeted for mid-November 2026, and it points readers to the UI Embedding recipes and Salesforce Developer documentation for implementation details.

Read the original at Salesforce Developers Blog (opens in a new tab)

Worth reading?