I think it would be a great improvement to animation to have such possibility to say 'If button#1 is clicked then move container#2 to y:254'

I'm trying the repeater but as this screenpart is on every screen that means I have to deal with repeaters on every screen ?

Hi, Benjamin.

The one thing which makes Indigo Studio prototyping different and faster is direct manipulation. As in, instead of using a dialog to pick a UI element from a document outline, you visually select and modify the UI element of interest. This approach aids in two ways:

• You don't need to remember names given to UI elements/Groups.
• As you are adjusting or modifying particular UI element, you can literally see what would happen without running the proto. For example, as I resize something, I can see whether I need to move other UI elements out of the way or not. In a nutshell, you are designing changes to a screen in each subsequent screen state. 

That said, we would like to to continue this approach. What Helena mentioned was allowing users to view the state of the screenpart or widget when used in a screen, and manipulate it in a similar fashion as shown above. Say you have a screenpart with two states (A & B). One idea is to surface the interactions defined on the screenpart state A, and using it to trigger a new screen state. This will create a new screen state, and also set your screenpart instance to State B. 

I am not saying this is available right now. Simply sharing an approach we are considering.

Ok I'll give a try !

Trigger interactions would be very useful as some of your competitor (like UXPin) have already this function (with some possible actions like 'Resize', 'Move', etc) and it's useful to acheive some interactions

Thanks