Web Apps: Public Preview - Build Apps in Studio Web

[evan.cohen]

Hello UiPath Forum!

Along with many other capabilities launching in 2024.10, we’re excited to kick off the Public Preview of Web Apps, which the community can now build directly within Studio Web. What makes Web Apps different?

• Web Apps are over 40x faster invoking workflows at runtime (yes, you read that right)
• Web Apps are easier to build (stick around and find out how)
• Web Apps use inline workflows as event handlers instead of rules
• Web Apps support easy debugging via breakpoints and watches
• Web Apps and their inline workflows are managed as a single package, simplifying lifecycle management for web app projects

To help you understand some of the amazing new capabilities introduced with Web Apps, check out this short video from @Milo_Shields:

Apps - Studio Web: Introduction to Web App Projects

Documentation and Learning Resources

To learn more, check out the detailed documentation:

Studio Web - Apps in Studio Web

Limitations

We’re still in Preview, so there are still some known limitations which we plan on addressing in the coming months.

What’s Next for Web Apps?

• Build CRUD Apps with native API connectivity: Activities as the Data Source for controls
• Build Action Apps with inline workflows, directly in Studio Web
• Public Apps
• Run inline workflows on self-hosted unattended robots
• Convert your existing Apps to Web Apps
• Support for controls like Edit Grid and Custom List

Your feedback is important to us!

We’re excited to learn from you! Share your ideas, use cases, suggestions and questions with us. We can’t wait to see what you build

[PeCour]

Hi @evan.cohen,
congratulation to your new product. But one point in the outlook “scares” me:

• Convert your existing Apps to Web Apps

We are at the moment converting all Legacy App to VB.net Apps. Which takes us days of work although we are using the migration tool.

Does that mean that at some point we must migrate all VB.net Apps to Web Apps?
Or is it only optional and VB.Apps stay long-term.

Thank you!

[ashokkarale]

@evan.cohen,

Web Apps looks promising but same question as @PeCour, is it going to replace Apps and we will have to migrate to Web Apps in near future? Also what’s the approx. general availability of this? So for new projects we can wait a while and directly start with it without creating legacy code now.

[reda (Reda_Marzouk)]

Hello @evan.cohen ,
Thank you for this new great way of looking at apps, it will encourage automation creators to use apps since now it can be used as interface for different automations.

I’m trying to use it, but I can’t find the new activties in studio web, the show message, set apps variables… don’t exist in my workflow when I’m defining new automation in events.

do you have an idea why that is?
is there an action to take on my side?

[evan.cohen]

@PeCour @ashokkarale The last thing we want is another migration, so from that perspective this bullet might be misleading. In an ideal world we make it possible to add inline workflows to your existing Apps and there’s no “migration” like there was for Legacy → VB. While this isn’t a commitment at the moment, we’d love to get your input on what you’d need from the product going forward in this regard.

We’re looking at rolling out Web Apps to customers in the coming weeks, with general availability by the end of the year (though this timeline is subject to the feedback we get from community and customers, of course).

@reda You may need to create an Automation Ops policy to enable “Preview packages and activities” as seen below: