General UX

Plug-In versus Editor

Plug-In: The chrome plug-in style design is indeed quite slick and easy to use. The fact that sign up happens through SSO within the browser itself without needing to go to a different website makes it quite easy to use.

Editor vs Widget: A full screen editor based UX can usually be very helpful for power users who would want to build more complex automations, as opposed to a small widget on the bottom right part of the screen. For example, if someone is working on a 13 inch Macbook (such as myself), editing on a small side widget becomes a bit complicated

Editor View

Agent UI:

The editor view looks slick and well designed. The UI is quite responsive and modern which I think is great and in-line with where I’ve seen most modern workflow automation tools go. The agent minimizing on the top right corner of the screen also makes it not obstruct / overlap with UI elements on that part of the screen.

Editor Views

Advanced Code Block View

To see the advanced code block, I usually have to switch to the advanced section, which then showcases the whole code for the whole program.

Is there a way in which I can see code alongside the block view such that I can do a side by side comparison of the code with the block view?

Flow View

Flow views can often be super intuitive, more so than block views since they’re more conducive to a typical operations person that visualizes workflows through a process lens and that’s also how their SOPs are designed. While I’m not advocating to copy from current tools, I feel that there is a ton of value in this view. See screenshot below:

⁠

Drag & Drop versus Click to Add:

Again advocating to copy a UX from another tool or continue to use what other vendors have used but in blocks based coding paradigm, there is definitely value in dragging and dropping from a tray of commands on one side of the screen.

⁠

. .

⁠

Moving around Code

The existing

⁠

command to move the code blocks up and down is definitely a good value add. However, being able to simply drag and drop is usually a lot more intuitive and helps with faster development, especially when the number of commands grows significantly and the block code becomes a lot more complicated

⁠

Orchestration

Agent Cursor

One key thing that really stood out to me was the agent not taking up my mouse but rather working off of a virtual mouse (which has Adept annotated against it). A general problem of former generation of workflow tools has been the agent taking up the cursor or working without a cursor especially when it is directly actuating UI elements

Background Processing

More of an open question, but I am curious if one can actually run these agents in the background while working on other tasks. This has been a long standing ask from customers with former tools and often requires a separate VM / compute instance where workflow automations need to be run. I’m not sure if either windows or mac architecture facilitates such background processing.