Robot is a great software, but it makes little sense to worry about the Dynamo link without finishing very important pending things before.
For example: The documentation doesn't explain things in a detailed-enough way (it's just a brief explanation of each GUI control, but there's absolutely NO documentation on what's implemented and what's not for each national code --mean you: I started a project with RC walls and I got the surprise that the only way for designing them was to choose the French EC2 code --and I realized after getting a cryptic message error, looking for it at the forums, and reading that the reason was that you need to choose the French EC2 --important things like this SHOULD be documented!!).
Another example: Global buckling analysis is undocumented. The only way for understanding it is to read research papers on global buckling and try to relate the formulas on the paper to the settings used by Robot... that's not serious, we should have detailed information on the algorithms and calculations really used.
Generating RC drawings is not practical: Are you supposed to export drawings one by one if, for example, you have 200 RC drawings? Why not automate this process within the printout composition, or with a similarly convenient approach?
BTW, the reinforcement of waffle slabs cannot be designed by Robot. It's a very common type of slab, so this should have high priority.
The RC reinforcement modules look like external apps, they look untidy: If you call the RC provided reinforcement module several times, it keeps the stuff you did in previous invocations, but in a weird way (sometimes you cannot modify previous stuff, and you need to delete it from the RC tree and create it again). The windows for provided reinforcement, required reinforcement, slabs punching, etc, are interconnected in a very confusing way... really confusing.
Maybe some of these points would be already solved if there was a good book showing how to use Robot for doing the complete design (with all the structural drawings) of a real-life building, for each of the materials supported: Steel, RC, Timber. But no such a book exists.
Fire checking in timber (EC5): Really confusing to enable the check (you need to manually type the number for the combination called "FIRE", or otherwise it won't work, and you won't get even a warning about it --if you choose "FIRE+" or "FIRE-" it won't work, it must be only the one combination called "FIRE" --again: this is not documented).
Timber joints: Some kind of timber joint design should be there, even if it's only very basic joint types.
Another very important thing is that, even if you have a lot of experience in structural design, it's very easy to forget to do important checks with Robot, because there's no button for checking that there are no pending errors in the structure (imagine this: you generate the provided reinforcement for columns, and even generate the drawings for them, but then there's an error on slabs, and you fix it but then you have to calculate the structure again: this would imply to regenerate the provided reinforcement for columns again, but you are not warned about it... and, in case a new problem appears in columns and you fix it, you have no way for knowing if the new fix affects other RC elements --at the end, is easy to get confused, lose the orientation, and end up with the wrong drawings for design: this risk should be minimized, with a better cleaner design of the RC modules).
Lots of things need to be implemented in some national codes.
So, to your question: I don't need Dynamo because I really need to have all these other issues improved before (how can I be interested in connecting Robot with Dynamo if the use of Robot for everyday structures is not properly supported in a practical way --or at least not documented? )
I hope I wasn't harsh, I truly believe this should be said, because Robot is a great tool, and I would love to see it shine.