There have been many good points raised, which really boil down to learning curves vs. tool approachability.
There are a few key tasks done in Hype that are currently in the realm of programming that would benefit from UI solutions. On my radar is:
- Looping timeline playback N times
- Binding time/property values between elements
- Easier toggle switches
Further, there are other features mentioned here that we also get consistent feedback about:
- Element collision actions (including dropability)
- Improved preloaders - both UI and fine-grained control on what gets loaded when
Another interesting aspect to think about is the role of Symbols. While right now they are basically just “Scenes within Scenes,” one of the original goals (cut short by time) was for them to provide a plugin-style solution where more expert users could create widely applicable symbols carrying their own code and behaviors which could be exposed as parameters. Other software like Sketch, Blocs, and RapidWeaver have systems like this. In this manner, users could use off-the-shelf solutions for a lot of tasks that require code (at least copy/pasting) now.
Anyways, this is all to say that we are listening and thinking about the problem space. In the early days of Hype, our original thought was that when users turn to code that represented a weakness in the application and would point the way for which features we should add. Clearly we have a big and healthy user base so it is overly optimistic to implement everything the community makes , but from a big picture we want to make sure the application never limits creativity.