Back to Basics

Over the past month or so lot of scope creep and details had made their way into the prototype. Some things, like the simulator, were becoming distracting and fragile. Other items were opening more edge cases that distracted from the core user experience of the canvas. Some examples here are we were approaching ~13 node types.

This meant everything you needed to add a node you had a choice to make between 13 items. Some of these nodes were intended to save time by composing several nodes together. However this was costing you time in the end because you need to decide and find the node you want and then hope that it was configurable in just the right way, a thing that was frequently leading to abandoning the more complex nodes after you found a dead end only to return to having to use the more simple nodes in the end.

All of this led to an experience that felt disjointed and messy.

A short list of things gutted (important to note that no required functionality was lost):

• ask node
• compliance node
• switch node
• filter node
• api node
• milestone node
• simulator
• flow type
• schedule send node
• policies
• cooldown
• pause/resume

Note that Segment style rule based flows are still a thing, they are moved inside the trigger configuration, this leaves the choice of “flow type” to the point where the user is ready to make that decision.

Give it a play: https://proto-workflow-builder-mk1.vercel.app/flows