Automagic Forum

This can be a way to make dense flows visually appear less crowded: in addition to the currently existing way to link logic flow from one action to the next by tap and drag of "+" to a new location, then selection "Action", consider making this method possible too: orphan actions, floating around on the work space of flow editor, can be "clicked" or "plugged" to another action,thereby forming a stack of connected actions. This is resemblant to Blackboxing a sequence of actions, by mostly hiding the interconnecting arrows.
I suppose this could come in two steps: first step is simply removing the visual arrow when placing two actions such that their box outlines touch. Currently, the arrow will be drawn in a loop, not improving visual appearance.
The problem this results in is, that it becomes impossible to distinguish between connected and unconnected boxes, when they touch. Therefore, connect them when one is placed below another, or side on side. Direction becomes an issue, possibly conventions of "top to bottom" and "left to right" could be a solution. Alternatively, the arrow goes from static part (the bulk of the flow) to the dragged part (the action we want to connect to the flow).
What I expect from this change is reduction of visual complexity with dense flows, easier editing by simply clicking unconnected components together, and more economical use of screen real estate, again with dense flows.

Not sure, if I catched your drift so I just throw blindly my own similar idea.

When connecting action box to another element and moving it so that the sides touches, the connection line should disappear but arrowhead should remain on top of the sides. When doing the same to condition, the arrowhead should be color coded for example green for "true", orange for "false" and red for "exeption". Color codeing would get rid of the appearing priblem that connection description wouldn't fit there anymore.

This would really benefit editing flows in small screens.

I like the idea to either connect the action boxes or optimize the connection arrows for such cases. I think that the loop arrow is quite annoying when two boxes touch, so I will try to get rid of the loop in a first step but still draw the arrowhead so one can see in what order the actions are executed. Color-coding the connections of a condition would be a possibility but I think it's not ideal when color is the only distinguishing factor of connections. Maybe adding just T, F and Ex would work in such "short" connections where space is scarce.
I will try to make some experiments when time permits. However it seems that Android 5 breaks some existing actions so it's my top priority to make the existing actions/conditions work on Android 5 first.

for indicating true and false with conditions, consider to borrow from gate logic, and draw an inverter circle at every "no" branch. Although that may not be very intuitive to non-technical folks, it requires very little space.

Martin wrote:Maybe adding just T, F and Ex would work

That might do. On horizontal connectictions their place should be on top of the arrow and on vertical connections respectively on left or right side, so they won't get mixed with element's text. Or if possible, dark text on the light colored arrow.

Martin wrote:Maybe adding just T, F and Ex would work in such "short" connections where space is scarce.

In many cases it would be better if the connection identifier could be placed near the source node.
Following the outgoing connection of a condition to a distant target node just to see if it's the true or false branch is sometimes tedious

Single tapping an action selects it, double tapping has no extra function. Maybe you can introduce double tap to select the whole stack of joined actions, so when moving the tapped action, the whole stack of actions is moved.

It appears that 1.25-dev from 2nd week of November implements some of this request already: some of the loops are gone, "Exception" gets abbreviated.