Agentforce NOW AMA: Build with React and Salesforce Multi-Framework

本站添加: 2026-05-28

[00:00:11]Hey, hey, hey.

[00:00:44]Don't need it.

[00:00:59]Hey, hey, hey.

[00:01:37]Hey, hey, hey.

[00:01:47]Hey, hey, hey.

[00:02:09]Hey, hey, hey.

[00:02:34]Heat. Hey, Heat.

[00:02:58]Heat. Heat. N.

[00:03:19]Heat. Heat.

[00:03:42]Heat. Hey. Hey. Hey.

[00:04:18]Hey, everybody.

[00:04:36]I'm just Heat. Heat. N.

[00:05:11]Every hey back hey back hey back hey back hey back hey back hey back hey back hey back hey back hey Heat. Heat.

[00:06:22]Heat. Heat.

[00:06:59]Hey, hey, hey.

[00:07:27]Hello.

[00:07:30]Heat.

[00:07:45]Hey, hey, Hey, hey, hey.

[00:08:31]Heat. Heat.

[00:09:12]Keep it up.

[00:09:45]Hello and welcome to another episode of Agent Force now ask me anything. I'm your host Charles Watkins, lead developer advocate at Salesforce and this month we have an amazing show for you today. We're going to be talking about my favorite new thing coming out of Salesforce with two of my favorite people. So let's hop right into it. All right. So, I am going to bring up our presentation here and we're going to talk about building React on Salesforce with the new multif framework runtime. All right, let's get it.

[00:10:26]So, as always, I want to remind you that Salesforce is a publicly traded company.

[00:10:31]So, you shouldn't make any purchasing decisions based on anything that you see here.

[00:10:38]Second, I want to remind you to join the Salesforce developers global community and interact with other trailblazers interested in building the future of the platform.

[00:10:53]All righty. I also want to remind you that we have Agent Force Now events like this live stream all throughout the month every single month. So remember to register for upcoming agentforce now events using the QR screen that you see on the screen right now. Go ahead. You can also use the sforce.co agentforce now link and it'll take you right there for code lives, AMAs, and guided workshops.

[00:11:28]So today, I promised you that we get to work with we get to talk with some of my favorite people here at Salesforce. We have them here with us today. We have Alice O, product management director, and Jeff Douglas. I'm going to bring them on stream right now.

[00:11:49]All right, here we are.

[00:11:52]I'll let you both introduce yourselves if you'd like to before we hop right into the uh presentation.

[00:11:59]Okay.

[00:11:59]>> Okay. I guess I'll go first. Uh so I'm Jeff Douglas, a product management director for Agent Force Vibes. Been a longtime Salesforce developer uh since 2007. Um joined Salesforce in 2015 to start this tiny little project called Trail Head. Some people may have heard of that before. Um did that for a long time and now I'm in product management.

[00:12:19]with one of the coolest tools I've ever been involved with my life, Agent Force Vibes. And I'm here also with my two of my favorite people, Charles and Alice as well.

[00:12:28]>> Thanks, Jeff. Thanks, Charles. Um, great to meet you all. I'm Alice O. I'm a product management director at Salesforce. I've been at Salesforce for four years. All four of those years in the platform space building out how you build apps on Salesforce. And that's one of the things that makes me super excited about today's topic which is the Salesforce multi-framework and how you can by code that with um agent force vibes because now the future of app building has become so different and so much easier and faster with all of the toolings that are available um with AI.

[00:13:05]So I'm really stoked to talk about them and share a little bit more and take any of your questions you might have.

[00:13:13]>> Awesome. Now we will be taking questions but as always we are going to start with a quick presentation from our experts.

[00:13:21]So Alice Douglas you know Jeff take it away.

[00:13:25]>> Sure. Uh next slide there. Okay so let's start off talking about you know what we introduced at TDX. So I think headed 360 represents you know a fundamental shift in how we operate with Salesforce. So you know we're moving from a UI first platform to an API first infrastructure.

[00:13:43]And what we're doing is, you know, decoupling the business logic from the browser. You may have seen some people say death the browser. But we, you know, we've made every Salesforce capability, you know, deployable onto any surface that's accessible via, you know, MCI, MCP tool, API, or even CLI command. And this allows, you know, AI agents to be able to execute these complex workflows while developers can, you know, be building with external preferred tools.

[00:14:08]Uh, next one, please, Charles. This is the the II chart here. So um you know let's start with something familiar you know we have these four systems that we all know and love at the bottom is you know your system context data 360 this is where all your customer data information resides up above that is customer 360 your system of work and where the clouds and the different industries the business logic work and then of course um one of my favorite system of agency you know agent force where the re agents reason and act on each other and on top of that is the system of engagement slack where it seems like everything happens nowadays.

[00:14:43]So but what what's new with all this header 360 is that on the kind of the right hand side all these are have you know any data lakeink you want to use any app any agent any workspace every layer is now you know open and programmable from the outside so so that takes us to where I want to talk about agent force vibe so let's let's see how you we can take the branch of headless 360 with agent force vibe so uh also mention again TDX so this is some of the things we announced at TDX our new version of agent force vibes it's built totally from the round up on open and um extensible SDK. We're going to be releasing 2.0 the next week and I know Alex is super excited with this. Tell you more about this, but it's going to be G in a couple of weeks. Uh you can be using it. It's going to give you much more development power than you've had before. Going to have some things like, you know, there's be different SDKs you can choose from. You can choose if you like using cloud code, you're going to be able to choose a cloud code SDK and be using cloud code inside of Vibes. or if you want to use more of OpenAI's SDKs, you'll have them, too. So, if you want to choose if you can't use one um SDK or another, it's not a brand new tool. You can just switch to a different setting for the provider and you've got that power inside that tool you so used to using. There's also a planner mode where you can actually do more of like a let's say um a large refactor or build an MCP or PC and you can provide some prompts or spec design and it'll walk you through the process of building that that task more of a jetic um runa case for that as well. And then we're doing that kind of build through swarms of agents and groups to paralyze tasks. And you can see that as well as you can build things much faster, much more complete. And how can you get it? as well. It's going to be available in almost every single, you know, pre-installed in the sandboxes. You can connect with different um ideides as well. There's going to be a number of rules and skills and MCP servers that are already in installed. We've got I think close now, Alice, if I'm wrong, let me know about like 60 skills that we are out of the box with about 70 so MCP servers tailored to do perform actions for you or get metadata on the servers or even know more about your server. So, one of the MCP servers is the new Salesforce catalog where you can actually um interact with your org and all the metadata even though it's not locally in your um project. So, you can reach into your org and you can find out is there a um is there a custom field in there that has some pickless values that I want to use and you can discover that using agent force vibes without that metadata being locally on your machine.

[00:17:16]So there's a lot of tools involved with that too for you know looking at or intelligence scaling. Um we've got a lot of tools for code analyzer that are built right in and you can run those to get you know best practices security involved with that as well. And then finally you know analytics you can look at what your team is doing in different orgs. So and that's all of course baked into the agent force trust that everybody knows and loves where we mass PII and P information and you know the models forget everything they they've done. So that way we're not training on your data and on your context. So um and then the last thing and this is probably I know one of Al's favorite is that in everything with VI we want to keep the human in the loop always reviewing and approving everything that's made before it gets committed. So that's a little bit rund down that I'm not sure do you want to talk more about you know React in particular Alice?

[00:18:06]>> Yeah. Yeah we can get to um talking about React specifically. Uh, thanks Jeff. And I think there's so much in Asian force fives that we're building out. Um, you all have the 2.0 pilot now, right? In the extension pack, so folks can try that out. Is that right?

[00:18:25]>> That is correct. And you'll see you'll see two actually extensions right now.

[00:18:28]Agent Force Vibes and Agent Force Vibes 2.0. They can live side by side in the same desktop environment. So go ahead and start playing around with that right now.

[00:18:37]>> Yeah, it's super exciting. So everyone on this stream like go check it out. Um so I'm going to switch gears and talk a little bit more specifically about Salesforce multi framework and you know previously and you all know this because you all are developers who are building apps on Salesforce your LDWC's and lightning components and um experiences on Salesforce. Building on Salesforce up to this point has meant that you are limited to, you know, two options, right? You have the lightning apps where you have a lot of the preconfigured apps settings and all of the capabilities that come with lightning and then you have experience cloud for guest user support or sites or marketing pages or um commerce experiences. And there weren't a ton of options in between it, right? if you wanted something that is um a little bit more customized or how they say you know pixel perfect or visually stunning as I like to put it.

[00:19:39]Um and so now with our support for multi-framework and with vibes and you know how you can now use AI to really customize the app experience that you want to deliver. This unlocks a whole different world for developers, right?

[00:19:55]because you can now build super customized um apps really quickly with Asian Force Vibes and other Vibe coding tools that you might be using. And so this then means, you know, for the UI layer on Salesforce as well, we want to make sure that we are remaining flexible. Um I know for some folks who are building with React, they're also building with Lightning and they're also building with Angular and what have you.

[00:20:23]And you want all of these experiences to kind of come together and have a cohesive experience. And so this is kind of where the Salesforce multi-framework was born out of um the desire to give you all with the tool set and the capabilities so you can build faster and um really have a customized experience really quickly with all the AI toolings that we provide. So if we go into the next slide, um some of the questions I've I've gotten a lot is around, you know, what does React support mean, right? What does it actually mean? And it can mean a SL a number of different ways. And so I'm going to start with if you have a React app or if you're already building in React, you have a React app somewhere not in Salesforce um deployed in a different hosting provider, you can bring now this React app into Salesforce and host it with us.

[00:21:16]And so we also provide um a lot of toolings around making it easy for you to build a new app with Salesforce. So things like um you know we have templates and sample apps that make that's so easy to access from Asian force vibes as well. So you can quickly scaffold your react app with templates and sample apps. It all kind of generates and sets up the SFDX project for you. We have the live preview. So as you are iterating and building or vibe coding in React, you get an instant feedback of what it looks like and the code that's generated. And then this is all part of your existing SFDX workflow, right? And the part that makes it really powerful is that now because your React app is hosted in Salesforce, you don't have to pass in like O headers or do manual integrations with APIs. All of that comes for free because the app is hosted um where your data is in Salesforce. And so that makes it really powerful and makes it that much easier to iterate and um move quickly. And not to mention, right, Salesforce handles a lot of the um governance and um permissions. You can reuse your workflows that you already have and the system of record being Salesforce being the system of record for all of your experiences. And of course with Agent Force Vibes, we make it super easy to vibe code it all too. Um, going into the next slide, this the first part that I just talked about is about how you can host your React apps, build a new React app on Salesforce. The second part of what we're also supporting is if you have React UI, if you have components that you want to reuse in your existing Salesforce apps, we also support um this type of micro frontend experience and pattern. And so you imagine a page experience cloud page where you have a customer portal and you have this one component that is in react that maybe someone else built or it's a design system or you know another person in another team that's building in react has built that you want to reuse instead of rewriting the same thing in LDBC and that's what microfen is about. We enable you to bring React components into your existing Salesforce apps in Lightning and Experience Cloud so that you can use it together with your LWC's. Um so that you have this microrend pattern where these components are all coexisting in the same place all done through our enterprisegrade security. Um, and that way you can have a very consistent experience across the page and they all look the same, right? For a non-developer person landing on the page, they would not know it's a LWC or React, they don't have to worry about what is the technology under the under the hood.

[00:24:11]Um, I'm going to pause there and jump right into road map. I know we want to have a lot of time for the questions.

[00:24:18]So, this our road map ahead. Uh we announced the React apps on platform in beta um about two months ago now. Um and we've been getting a lot of great feedback from y'all. So keep them coming. We love getting feedback from the developer communities. And we also have the micro frontend experience available as developer preview. And that we are targeting to bring into GA along with some of the many other features we're working on for Dreamforce. Um that said, the React apps on platform we're um working towards uh general availability in June. So s coming up super close along with agent force vibes 2.0 that Jeff talked about. Um in July we have some more features that are coming up like packaging and hybrid visual editing that we'll have in pilot and beta. And we're hoping that all of this we can bring to general availability for Dreamforce September time frame. And I know a lot of people have asked um is it just react you know it's called multi-framework are we going to support other frameworks as well and the answer is yes uh we are working on angular support as the next framework um UI framework to support and we're hoping to release that um as beta by dream force time.

[00:25:36]All right I'll pass it over back to you Charles.

[00:25:41]>> All right awesome. So, let's get into the Q&A. And we have a ton of questions.

[00:25:48]So, I'm going to just go ahead and bring us all up here so that you see the experts names and you also see us. Okay.

[00:25:57]So, remember this is a live show, so please do submit your questions. I'm going to grab a few questions. Oh my gosh, we have so many questions. Let's let's start from the top. Um, some of these have already been answered, but let me see here. Here's a great question from uh Sally. Oh, cool. Um, any advice for React beginners? Uh, is using public React learning materials good enough or are there any differences between regular React and React on Salesforce that we should be aware of? So, I think um, Alice, that one's for you.

[00:26:36]>> Yeah, this is a great question. Thanks Sally for submitting the question. Um, we've been getting a lot of questions around is building on React with Salesforce different than how I've been writing React if they've been a React developer for a very long time. Um, is it very different? And the answer is it shouldn't be, right? Um so the goal here that we wanted to address was we want um both React developers or you know in the future Angular and other framework developers to be able to build with Salesforce. And so one of the things that we were super intentional about is making sure that um any React app that you're already building outside of Salesforce, it makes it easy for you to bring it into Salesforce, use it with along with all of your other Salesforce apps and toolings and workflows. And so, you know, some a lot of the basic um React web development classes or resources are yeah, you should absolutely leverage those. And as you build those React apps, you should also be able to host those React apps in Salesforce. Some of the Salesforce specific things would be around more of the developer workflow. So things like, you know, SFDX project structure, which is about, you know, how you structure your code. Um the metadata that Salesforce uses to um to essentially like find your React app. Um so those are you know Salesforce specific things and those are there even without um for any kind of hosting provider you use like they uh need some way to easily discover your React app. And so yeah to answer your question um definitely feel free to leverage all the beginners React courses or resources that are out there and um deploy them with Salesforce.

[00:28:24]Yeah, I think we spent a lot of time and effort trying to make it easy to more or less not really port but bring your existing apps or learn how to write new apps on the platform so that if you're a React developer, it's not a big lift to get your apps running on Salesforce by just knowing some of the flat platform inaccuracies of like different type of web platforms.

[00:28:44]>> Another question here from Apex Genius AI. Does Agent Force Vibes utilize the metadata experts tool to create metadata or just execute metadata actions like call a flow or invocable apex? That one's for you, Jeff.

[00:29:03]>> Yeah, I mean is this really a person asking this? Is this an AI genius asking this? I want to know. So, but no, it does actually use the metadata extra.

[00:29:11]There's a couple of MCP server that we utilize to give the models context on how to build Salesforce metadata because of course you know not every model knows the incon intricacies of building XML from the Salesforce platform. So we do so we have a number of skills that we've created. There's about 70 or so skills now and they're all available in the Salesforce open source repo. It's uh in the force.com environment. I think it's called SF- tool skills now. SF skills.

[00:29:38]It used to be renamed something else but it's been changed. And you can use those skills from there. And so when you actually are doing like let's let me build a custom object or build a flexi page. It's going to call that metadata experts server grab the context for how to build that metadata type and provide that to the model so that it knows how to build you know this metadata with more efficiently and also hopefully it's going to be um higher quality to develop to deploy the first time.

[00:30:07]>> Amazing. Okay. Um, another question, this is a question that came in, um, that was presubmitted.

[00:30:16]Um, and this one's for you, Alice. Um, what MPM limitations will there be for Salesforce multi framework? What is the process like for submitting requests, having versions available? Namely, will tell when version four and not just three be available?

[00:30:39]That's a good question. Um, so kind of at the high level, um, any mpm packages or modules that you're using to build your React app, um, you should be able to leverage them from the React app that you deploy on Salesforce. And so um and to kind of deep one layer deeper um how we are loading we on the platform are loading these react apps that you deploy is essentially once you have the um the react code um you run and you know if you're using beat plugins you run an mpm run build and you build the react app and all of this is done locally um and then once you have the build artifacts and the directory um you still do deploy all of your source code uh source code, but um when we uh serve it from the Salesforce platform, we're essentially serving the files that are in your directory, right? And so um we our goal is to support any standard MPM ecosystem workflows as much as possible. Um but of course, um we want to balance that with security and performance and how we support them, right? So, um it's a it's a balance that we're managing now, but um in general, any of the, you know, toolings that you're using within your React app, um you should be able to use and um because you're building all the app entirely locally and then serving and deploying that to Salesforce and we're just serving what you provided us in the desk directory. Um so yeah I think things like tailwind something that is on our radar and we support um that today um and we know customers uh want to use modern ecosystem. So um that's I think the exact version availability and how we continue to support all of the future version is something that we're talking through especially with um some of the things like packaging. Um but yeah, that's something that we are um we want to make sure that that flow is super easy for our developers.

[00:32:45]>> Awesome. Another question here. We got Let's see where is this question. I have to find it. It's a really good question.

[00:32:55]Let me see where is it. Where is it?

[00:32:56]Where is it? It's a question about Vibes 2.0. I'm sorry. So many sometimes I can't always find them easily.

[00:33:07]What was the question is Vive awesome?

[00:33:10]And the answer is yes.

[00:33:13]>> Always yes.

[00:33:15]>> Okay. Um here it is. Um with Vibes 2.0 allowing you to essentially bring your own harness. Will there be more concentration on Salesforce provided well-defined skills plus uh MCP over an alternative clientbased experience? And this one was presubmitted from uh Beach Horn.

[00:33:36]>> Oh, from Beach. Thanks, Beach. Great question. Uh, fantastic question. So, yeah. So, we're going to have multiple SDK providers. So, you'll have, for instance, OpenAI, Anthropics, we'll have client SDK. They're finishing up their SDK now. We're have Mastra. There's also talk about maybe MR SDK as well. A lot of people in the UK in the in Europe are looking for that as well. Um, so bring your own SDK. I'm not quite sure how that would work. um because there's a lot of stuff tied to the different parts of the gateway that the SDKs um are from where we we now have an agentic SDK that a lot of different platform ser and so that's be like one SDK that will be wrapping around different ones as well. So not necessarily a a wrapper but it'll be implementing those actual SDKs.

[00:34:22]So I mean we are we are saying like this is the way the the preferred approach is using these skills these MCP tools. Um, so we'll be having quite a few more of those. I think you're going to see a lot of the MCP tools are going to be moving towards skills. That's kind of a trend in the whole industry. You know, MCP servers, we thought what, six months, a year ago, we're going to, you know, save the world. And now there's a lot, you know, some issues with that with token bloat and, you know, being selective on which tools are called by different models like that. And so you're seeing a lot of people who are moving their MCP tools to either skills or just straight CLI commands. Um, and we're kind of doing the same thing here. So, that's going to be the prescriptive way we're going to be doing things right going forward as well. I hope that answered the question. It was a roundabout way to say yes.

[00:35:10]>> Love skills.

[00:35:12]>> I just write skills when I'm free, right? Just writing >> vibes. Write skills for you, which is even better. So, that's great.

[00:35:19]>> Hey, that's skill for writing skills. I would I would use that skill.

[00:35:24]>> Okay, we got a question from Aditia Singh. Um, besides reusability, what other aspects can we optimize using React? Is Agent Force Vibes 2.0 optimized to handle Reactbased changes and support additional React implementations?

[00:35:43]That's for everybody.

[00:35:46]>> Yeah, maybe I'll take the first stab and pass it over to Jeff. Um so one of the um areas where React is really awesome is that what I mentioned around you know flexibility right so if you are already building with React um but also React has so much resources out there in the web there's so many web developers that are already building in React there's a lot of you know Stack Overflow resources and the developer community and so all of this are available to you as a developer if you want to build and write code in React and run into any issues or need resources and support, right? And also one of the other things is as we go into you know vibe coding with agent force vibes and any of the AI toolings of your choice um there's so much resources out there around you know building and writing coding react that um you might be able to do some very niche and um very specific things which I think if you're building like a you know a normal well not a normal but like a standard e-commerce app or a web page uh you may not run into. But if you're looking to do something very specific or uh a very custom uh workflow experience, you might be able to have a better chance getting that right with five coding in React versus um just based on the amount of resources that are out there in the web that AI is five coding off of, right? and and so um I think that's one of the areas where React is really a great choice if you're looking to start building an app. Um, having said that, if you're looking to build something very specific to Salesforce and um, specific to your lightning app or experience cloud app, those are areas where I think, you know, you can continue to build with our existing lightning ecosystem and lightning frameworks and th those are kind of where lightning web components would really shine, right? Um, also I think one of the things that um, uh, one of the customers I mentioned was for React there's um, a lot of performance tuning and a lot of libraries to help with that. And so if you were looking to have very specific um, hit very specific performance goals for your app experience, uh, you might have more resources in that way as well. And I'm going to pass it over to Jeff to talk about the Vibes experience too, but we've done a lot of work to make that great. Yeah, you said most of the great things I was going to say as well. So, thank you very much. Much more eloquent than me. Thank you. Um, so yeah, I mean, so Vibes, you know, it's really good at writing React. I mean, we showed that what last Dreamforce Alice when we did the whole React did demo back then.

[00:38:27]Vibes is really good at at at writing React. Uh, the models know how to write JavaScript and CSS. Um, so we're just leveraging that as well. What I think what makes vibes a better tool for writing react than let's say anything else is that you know there's a lot of intricacies on how to write react the platform and some of these other models or agents don't necessarily know that right now they have been trained in that but you know the skills and MCP servers that we have involved with this whole tool chain of vibes can write react well for the platform so I mean we think that that's the way going forward is going to be you know react UIs for applications for most most companies so we're super excited about that and also you know the new frameworks that Alice is going to be delivering in the in the near future >> new shiny things.

[00:39:15]Yeah, we've done a lot of work to optimize the experience with the vibes to react and I think a lot of the skills and MCP servers that we provide from Salesforce really help that experience and also keeping in mind right if you're um vibe coding from vibes uh it has the context to all of your Salesforce orgs so it makes building with Salesforce that much easier and require that less prompts right >> yeah let me touch on one thing also that reminded me so we have a new server it's called the um Salesforce catalog. So you can access you a lot of your metadata without having it locally. So let's see you know a lot of these larger orgs as a developer you don't pull down your entire or you know the manage packing everything but let's say you're working on an application you have to create some custom object and you're like well does this custom object already exist or if there is a existing uh let's say field and a custom object or an unmanaged package that you want to use you don't have that down locally you can use the MCP servers the metadata grounding servers to actually introspect your org and see what's there so if there's a manage package that has a pick list values on a custom field, you can pull down those pick list values and use those in vibes without ever having to have the metadata locally. So that allows us to reach into your organ kind of interrogate what's in that organ, what the configurations are, >> which by the way is huge. Like I've definitely tried vibe coding with like other tools, right? Like cloud code or something, but you have to tell them a lot of context before you can get something working. But once you do, it works. But it's just that first beginning. It's like connect to the or read everything that's in the or you know. So >> it is awesome.

[00:40:55]>> You save a lot of work from Asian force vibes. I have a video coming out showing folks how to set up claude code for Salesforce and you Salesforce development. You do got to pull the skills. You got to set up MCP servers.

[00:41:07]It's good amount of work. Agent Force just works out of the box. Um a question from a LinkedIn user. Will the React component be able to communicate with LWC/oraura in parent child containment?

[00:41:25]>> Yeah, this is a great question. I love this. Um, so this is kind of getting to the microphone and pattern experience that I was talking about earlier. Um we like to think about react support on platform as both supporting react like full react apps as well as supporting react components that are hosted in and used with LWC's in the context of lightning apps and experience clouds. So the microrend um product that right now is in developer preview that will uh we're talking to G and Dreamforce in September. What it does is essentially it acts like as a kind of like an LWC wrapper around the React UI so that it can then you can you know drag and drop it from your lightning app builder or your experience builder or use it along with the rest of your LWC components in your lightning apps and experience cloud apps. And so and in that wrapper we provide the APIs to make the eventing and passing you know any communication a lot easier. Um, I think that's like post message under the hood. Um, and also being able to drag and drop that component on the page along with LDBC's and have it be interactive. Those are the kind of experiences that we are um planning for for that we're building um for the microphone and experience. So you can kind of think of it as you have your React component. You're essentially creating a custom custom LWPC and wrapping it um with LBC um with the React component in it and using it as you do and as you use any LWBC from a page.

[00:43:08]>> Amazing. So it sounds like sounds like a yes like you can you can talk to um LW you can talk to or LWC um as a child component which is great. Here's another question from Ari and Kumar. Um if you were designing a Salesforce app from scratch today for the next five years with agent force in mind which parts would you intentionally avoid building in React and why?

[00:43:38]That's a very specific question. Uh >> there's a lot of things you wouldn't do in React.

[00:43:47]>> Yeah. Yeah. Huh. That's a great question. Well, I do not claim to see the future of the next five years. Um just five months. We can barely see five months ahead of time.

[00:44:00]>> Exactly. Yeah. I I mean I think Jeff and I, you know, I think there's a lot of things that are just changing a lot, right? And especially with AI, we were just talking about how like skills are now taking over MCPS and I feel like that happened within a couple minute like months. So um anyway going to your question um so if you were building an app today um from scratch with that is integrated with Salesforce that uses data that you have in the CRM um that is kind of forward thinking for to build a business on top of. I think that's kind of what you're getting at. Um, one of the things that we are we have talked about that we that is kind of on the road map slash we're um trying to be more opinionated on is about serverside support around React. And so um and what I mentioned earlier is one of the things that we are unlocking for React support on platform is you can build your React app completely separate from Salesforce and then once you're done you build the run the build locally and then deploy the source file and this this directory into um your org and we serve it directly from your disk file. Right? But if you want to build a React app that has a lot of server side configurations.

[00:45:18]So um you know serverside rendering is one or making any other serverside API calls that that then um changes the behavior of the React app experience. Um that is something that we are currently not planning to support. Um and again I'm I'm saying this because I cannot see the future. Five years is a long time.

[00:45:41]Um but that's something that not we're not keeping on the road map. And the reason for that is a lot of the times, you know, when we think about where the modern web is heading towards, we're moving more and more towards a very lightweight um development experience and frameworks. And so a lot of um you know, VIT is super popular and that supports, you know, um React and Spel and Vue and kind of that category of frameworks. And um we're when you see the modern frameworks that are being used to build apps today um like I forget what the page was called but kind of the surveys um you can see that the web development is moving more and more towards very lightweight development um so that you can directly serve all the static you know build files um directly to the browser and so that's where we're putting our focus on um so that it enables us to unlock block more frameworks in a lightweight way. So I know we talked about you know we have React support and we're uh working towards Angular support from there unlocking other frameworks like you know Vue or spelt or any framework that I may not have heard of um kind of being able to load them in the same way and pattern um is really powerful for us as a platform and so that is something that we're kind of focused on right now. Um, having said that, uh, maybe a year or two from now, we'll start to add suicide support. Who knows? But, um, if I were to kind of put my, um, what's the word?

[00:47:18]Cast a ballot. Um, that will be something that I would avoid. Um, but besides that, um, honestly, one of the things that we want to move towards is, you know, kind of moving with the modern development workflows and experiences.

[00:47:33]So, and we as Salesforce want to stay ahead of the curve as well. Um, if not at least go with the curve, right? And so, we want to make sure that all of the modern ways that developers are building today, we are able to support that um pattern. Um, so that you can build quickly, reuse all of your apps within Salesforce along with the Salesforce ecosystem.

[00:47:55]>> I think also one thing talk about is um what not to build like what to build.

[00:47:59]So, you look at React as more the presentation layer. You don't want to bake security into that. You want to bake logic into that. You know, you want to build with the Salesforce standards and practices. I had one PM a long time ago said the first rule of writing code on Salesforce is to not write code on Salesforce. If you can do it declaratively, if you can build flows or if you can build um validation rules or you know custom objects, you know, declarative should be first. we want to put a lot of your your work at is the CL part and only write you know the presentation layer or the UI or any custom logic in with the code if you absolutely have to. So I would recommend you know Salesforce development best practices um you know keep those different tiers where they belong and the custom objects and the validations and the security and the logic all there and you know the react is more of your presentation layer.

[00:48:52]Yeah, I mean it does feel like we're moving more and more towards a very metadata driven um ecosystem and app flow. So >> you might say headless. You might say headless, right?

[00:49:03]>> Boom. Mic drop.

[00:49:06]>> And that's the end of our No, I'm kidding. Um >> now, >> right. Um we have one we have another question here from Sally. Um, can we track React UI bundles metadata on DevOps center or not? Would either of you happen to know?

[00:49:28]>> I'm not a DevOps center person.

[00:49:30]>> I would say I would say no. What What do you think?

[00:49:34]>> Yeah, UI bundles are not yet a first class metadata type in DevOps center.

[00:49:40]Um, but it is something that we're working on. So, keep an eye out for that. Um, and we want to make sure that these all connect and integrate with the DevOps center. Um, but I think that's in the works. So, that's a great question.

[00:49:54]Thanks for asking that.

[00:49:57]>> Side note, like complete, not a complete tangent, but like slightly tangential. I was building a Salesforce multi framework app the other day and I noticed that when I deployed, I was deploying my source, like my actual source code to Salesforce and I could pull it down, which I thought was pretty cool.

[00:50:15]It's pretty neat feature.

[00:50:18]>> I would would have expected that the only thing that got deployed was the disc folder, but >> yeah, I was having that recently as well where I just deployed directly to my org and then I realized, oh, I didn't update my git and so now the two were kind of out of sync and so I was pulling the changes from the org and and pushing it to my git, which is, you know, totally not recommended, right? this is just my, you know, personal project. Um, but yeah, I was like, "Wow, it's just so much easier to deploy now and iterate."

[00:50:50]And so I forgot to make commits to my git, which is crazy.

[00:50:55]>> Totally.

[00:50:56]>> So, you're saying you're not a developer, Alice, I'm trying to say, >> only a part-time at night.

[00:51:04]I'm just kidding.

[00:51:06]>> Okay. Um, let's see here. Um, here's another one from Arian Kumar. Keep the good questions coming, my friend. If you were starting your Salesforce journey today, uh, what road map would you following follow considering Agent Force? React and AI are growing so fast. Woo. Yeah, it's kind of like kind of like get on Twitter and just hold on tight, right?

[00:51:30]Um, yeah. I mean, I I would do more things like um know how AI works. I would start using agent force vibes just to start building stuff and see how you use the tools with different frameworks with you know you can use agent script to build agent force agents of course react as well there's a lot of things you can do with it and I would just start getting your your your feet wet in it and get working with it and ask a lot of questions like if you don't know how to do things you don't know how to build so with react how to get started you can always ask vibes how do I how do I do this and it's going to explain things to you um that's one thing I always do was just start learning how to build um with AI. I remember someone told me one time um you want to be the person telling AI what to do, not AI telling you what to do.

[00:52:18]>> Alison, >> yeah, this is a great question. Um and I might have like a slightly different answer here. Um, so I think especially now with AI, um, there's new toolings coming out left and right and like Jeff said, we're all following the news every day and like what's the new thing that was announced like what's the new model that came out, you know? Um, and I think one of the things that I really think is valuable with building with Salesforce is that we have a lot of support for the specific industries that you might be building for. So depending on your use case um you might be building for a customer that is in healthcare or you might be building for customers that are in you know science fields or um what do we call life sciences or or marketing and commerce right and each of these industries have very specific requirements um I think when you get to the very foundational aspects of how do you build a web page um that's you know of course very you know similar across all the industries But once you get to like spaces like healthcare um some of the niche requirements like HIPPA compliance or what have you become really critical and I think that's where some of the Salesforce teams are working on you know agents that support those specific industries and so I think just thinking about um what are the values that you get with Salesforce um in like depending on your use case and what you're building um there might a lot of very niche but very useful tool sets in the Salesforce suite of products that we provide. And so um and I think for Jeff and I, we uh we're kind of driving and making it easy for you to leverage all of the Salesforce offerings when you build an app with Salesforce, right? So, um I would really kind of pay attention to and think about what are the use cases driving um the apps that you're looking to build. Um and like what are the specific Salesforce offerings that you can use um that's good to have in the back pocket. Um so that you know there's parts that you can build um and vibe code and build super quickly. Uh and then there's parts where it takes a lot of prompts to rebuild or kind of um go through all the requirements and have that experience. So I would look out for those and that would be kind of my answer to your question.

[00:54:47]>> We have uh another one here from Satish Kumar Bilisanti. Um when deploying React components within native Salesforce developer experience, what kind of measures need to be taken?

[00:55:02]Yeah, I love this question. Um, so if you are, let me kind of maybe run through what I do, right? Uh, and or any developers can do, right? Um, if you're building a new React app, um, you so in the in the earlier slide, um, I had a screenshot. I don't know if folks might have seen it but from uh the VS Code extension of Agent Force Vibes we have the welcome page and from there you see different tiles where we provide a super easy way to scaffold your project. We also even provide some sample apps that you can get started and so you can quickly click on those to scaffold your project. Um that is all set up. Yeah, there you go. Thanks Charles. uh that h gets you all set up and ready to start vibing or you know writing code manually and get started right so you don't have to set up your project structure yourself right but essentially it's running the like generate template generate command on the back end um once you do that and have all of the you know react code written your app is looking good you preview everything it's all awesome use graphql to connect to all the data that's in Salesforce. Now I'm ready to deploy. Um, so what I would do is I run an MPM run build to build the React app and you have the build artifacts and from there you can run um SF project deploy to deploy um your SPX project or the specific files that you want to deploy. Um, and that will and of course go through your authentication and connecting to your or what have you.

[00:56:46]And then um there you have it. you'll have the React app deployed in your org.

[00:56:52]And so it's as simple as that. Um, and then from there, you should see it in your org. Um, you can go to the app launcher and you should see that app show up in the app launcher. Click to open the app and you should see the React app that you deployed into the or if there's other things that you want to update, you know, rinse and repeat. go back to the command line or vibes to you know make any updates um build run the build and deploy um and yeah that's kind of the that's the flow for uh developer experience and I think that's a common flow for um a lot of the React developers today. Jeeoff, do you have anything you want to add here?

[00:57:35]>> No, I think you you crushed it as usual.

[00:57:40]>> Amazing. Okay. So, let's see here. You know, thinking about that, I when I use uh when I build multi framework apps and I'm just always playing with it. I'm always messing with it. You know, if I find an issue, I try and file it. Um I found that >> you hear from Charles a lot.

[00:57:58]>> They they love me. They probably hate me just a little bit because I'm >> We all love you.

[00:58:04]>> Hey, fix this. Can you change that? Um, I have found uh that you oftentimes you can use the same um workflows you use for general web development if you've ever done that. So, a lot of the same things work, right? Like if you if you're worried about, you know, your packages that you're using and you're upgrading non- Salesforce packages for development, you can add a minimum release release age. Um, you can do your you can do your development in dev containers like try all these different things. And the really cool thing about what Alice and Jeff are building is that they don't really at all fight um modern web standards. They adopt them and they use them like really really well, which is why I'm such a big fan of their work. Um and they're two of my favorite people. Um so, you know, you don't you just take the same you take the same um action you would otherwise in my experience. Um cool. So here's a question from Adika.

[00:59:08]Can the existing architecture support microrend React implementations?

[00:59:17]>> Yeah. Um I'm curious what you you're referring to about existing architecture, but I think I'm going to guess that you are you currently have Salesforce apps that you have built out.

[00:59:31]you have some flows, maybe you have an experience cloud site that is a you know commerce site or something like that.

[00:59:38]I'm just kind of making assumptions here um about your existing architecture that you might have. Um and yes, the answer is the goal here of the React microphone and support is to enable just that where you can use React UI. So let's say you have, you know, a React app or a couple of UI components somewhere else, you know, hosted somewhere else and there's a couple of them that you want to reuse from within your, you know, Lightning apps or from your commerce page. There's like a little button that you really want to use that you don't want to recreate or maybe there's a drop down that you want to surface on that um commerce page. then you can use micro finance to embed those and bring those in and um serve it from your app or your existing Salesforce app. So um I think the um I mentioned before the how micro finan works is that it's essentially kind of like an LWBC wrapper so that you can embed your react UI into the LWBC wrapper or the microphone and wrapper and use it as though you're um you're loading an LDBC from your page. So you can use your builders to load it directly from your um lightning page or experience cloud page or you can use it like a custom component that you can load from a particular area that you want to add the code into. Um and one of the things that we're so this is in developer preview now and one of the things that we are actually working towards for RGA and Dreamforce is that um because we have um support for React apps within Salesforce. Now we also are building this microphone and experience to also kind of use our same UI bundles um implementation. So the react UI that you're bringing into um microphone ends and embedding into experience cloud um you can also host that react UI directly from Salesforce as a part of your UI bundle and then set the target for that to say you know expose an experience cloud or lightning app etc and it exposes that particular react component or an app into you know the target of your choice like experience cloud or lightning through micro finance. So yeah, we're actually really excited about this. I know at TDX a lot of folks have come up to me and are like, "Wow, this is so awesome." Um because that's what they were looking for, right? And so um it really kind of um marries the story of you're currently building all of your apps in Salesforce with Lightning Experience Cloud, etc. Um and how can you also leverage React within the apps that you already have? And that's totally what we want to support of reusing any of the existing UI that you have so you don't have to rebuild things.

[01:02:40]>> Quick followup to that one. Will the React component be able to be exposed in agent force agents?

[01:02:49]>> That's a great question. I actually got this question recently and >> Yeah. Yeah. And yes, I think um so I think what you're seeing here is if the React um if the React component you have that built in Salesforce or hosted in Salesforce and you want to expose this in the agent that you have built out in Salesforce. Um and we actually um have well so I guess the question is if you want to directly pull in the component itself or the data itself from that conversation right because if you're talking to an agent and um like you're essentially prompting it right saying like hey tell me about the opportunities that were in my org that's assigned to me or opportunities that closed in the past month or etc. And so like I'm curious if you would want to expose the full component or um if you're looking for just showing the data and generating the responses. So I think >> we had that same kind of question um in the team as well is like we want to be able to provide the same information and service it different ways depending on what that presentation may look like. So maybe all of our different services adhere to some contract about what kind of data it receives and then it knows how to display that. So maybe it could be some kind of react application or components running agent force to go through you know maybe a series of like a wizard type process or collect information and so we have been talking about that you know how to make a thin wrapper for presentation and maybe that would be some type of react component.

[01:04:33]Yeah, the headless experience layer thing. I don't know. Um, >> yeah. Yeah.

[01:04:39]>> Cool. Uh, another question. I think this is in response to something you uh said earlier, Jeff. Um, as agent force becomes more autonomous, how do you see the balance evolving between declarative tools like Flow and custom frameworks like React, LWC, and enterprise app architectures?

[01:05:00]>> That's a fantastic question. I was just talking to some about this exact same thing. It's like um you know when when do you want to use something declare like flows or build something like react or lwdc's I guess it depends on you know what your standards are for your company. Do you have do you have mandates that say it's for automation?

[01:05:18]We use flows because that way our admins can go and maintain these or business users can maintain as well or or are you more of a you know a procode heavy kind of shop where you know you let the model do a lot of development in react or in apex or lwc's I guess just depends on you know the project you're working on what you want to do. So I don't know if we actually have a mandate like flows are always better or lcs are always better. I think it's based on the use case of your project or or your company what type of a governance they have for something like that.

[01:05:51]>> Yeah. Yeah. I know like folks who are also building like and vibing metadata as well like flow metadata and also then putting like UI on top of that. And so yeah, I think one of the things that Hela's really unlocked is this abstraction layer of, you know, they're all decoupled, right? And so you have the UI layer and you can have any UI that you want um that's built on top of any metadata and um that also uses data that is in CRM. So I think you have a lot of power to you in using >> if you're using a lot of flows you know flows can get a little unwielding sometimes. Um, one of the great things about Vibes is you can automate, you can spin up, you know, invocable Apex classes really easily. So that way you can use flows with Apex for some of the business logic that's testable or a lot of times, you know, you may want use um, Vibes to go in and look at a flow and tell you what's going um, document that what that flow is doing and kind of give you insight into it and actually, you know, use it to debug, you know, operations. You can have it, you can have Vibe say, I'm going to go ahead and insert this record and it's going to run this flow and then have Vibes go and query the results and make sure that the records were set up correctly based on the outcome of that flow. So, you can use it a lot of different ways with declarative workflows as well.

[01:07:13]>> Okay, final question and this one comes from Regul on YouTube. Uh, can we publish React apps in App Exchange?

[01:07:22]>> Oh, good question. I mean, that's what we want. I mean, we got a lot of ISVS who want, you know, beautiful looking UIs. So, I'll let I'll let um Alice give you the lowdown on that.

[01:07:32]>> Exactly. I think Jeff and I have heard from so many ISVS and partners um this past week, month and a bit um since TDX launch on wanting to package up React apps. Um the answer is not today, but this is on the road map and we hope to bring you exciting news for Dreamforce.

[01:07:50]Um, this is something that we're actively working on to support publishing React apps on App Exchange so that our ISVS and partners can build um, React apps and publish them on App Exchange and share it with other um, Salesforce customers. And being able to share um experiences, apps um across uh customers across even users within the Salesforce or is something that I'm really excited about um because right now a lot of people are vioding apps and building a lot and building very quickly and there are skills that help you do that etc. And so I'm really excited about kind of what this enables for both developers but also vibe coding developers right who are not you know quite developers but with the help of you know agent first vibes we're able to build and publish apps really quickly and so I think this world of you know we have so many apps and now how do we make it super easy to share with other customers and other users is a really exciting space right now. So, I'm really excited to hope to have great news for you um for Dreamforce.

[01:08:59]>> Amazing. Okay, so we're going to wrap things up. Uh I guess before we end, like where's the best ca where's the best place for folks to follow you for news on Asian Force Fives 2.0 and Salesforce Multiframework? Are you on social?

[01:09:14]>> Uh I try to be as little as possible, but I'm required to. Um but yeah, you can follow me on LinkedIn as well, a little bit on Twitter. Um, we there is a good spot to follow information for Agent Force Vibes. It's there's a short link sfdc.cov that has all kinds of announcements and demos and news and tutorials and videos that we put out. So that's a great place to follow us as well. But then of course on LinkedIn most from Salesforce is on LinkedIn.

[01:09:41]Yeah, I would definitely say follow all the developer community channels um the Salesforce developer LinkedIn page and all the uh communication channels there for any updates. Um feel free to also follow me on LinkedIn. Um I think we have a couple of more webinars and info sessions that are scheduled um leading up to Dreamforce. So definitely follow along and especially Oh yeah. Yeah.

[01:10:05]>> Oh go ahead.

[01:10:06]>> Oh yeah. especially if you are in um you know different time zones and different geos. We have the world tours going on and so we have different product managers who are different geos who are going to be also um showing off like what we're working on and the road map and answer any questions. So definitely check those out >> and if you want to know the the real scoop about everything, you need to follow Charles on LinkedIn as well.

[01:10:32]>> Great advice. Great. See, that's why you're That's why y'all are my favorite people. Um, y'all know me well. Okay.

[01:10:40]Amazing. Well, thank you both for sharing your time, your expertise, your thoughts with the greater Salesforce community. Um, let me pull back up my slide real quick.

[01:10:55]So, I want to remind you all, remember what Alice said, join the Salesforce developer community. keep the conversation going. Um, if you didn't get your question answered here, um, ask them there. Um, I believe both of you are members of the Salesforce dev community, right? So they can they'll be looking out for questions. Um, so thank you all again so much. Again, follow Asian Force Now um, community. Make sure that you are subscribed to our events.

[01:11:28]We have another awesome AMA coming next month. Thank you all. Have a great rest of your day. Take care.

[01:11:36]>> Thank you everyone.

[01:11:38]>> Thanks everyone for tuning in.

[01:11:40]>> Talk to you'all later.

[01:11:41]>> Bye.

[01:11:58]Heat. Heat. N.