"- Are there any plans to have some user-facing API for plugins/scripting? Professional workflows vary widely and automation helps a lot." Yes, a scripting API

"- Are there any plans to have some user-facing API for plugins/scripting? Professional workflows vary widely and automation helps a lot." Yes, a scripting API is planned. The GUI is being designed from the ground-up to where every action will go through an event system, so script will be able to do pretty much anything the GUI can do. A lot of the backend components will also be separated into a separate repo under the RustyDAW project, allowing someone else to create their own DAW with their own GUI if they wish. "- How flexible the UI is going to be? Multi-monitor setups of different configurations are very frequent in studios, free docks and/or floating windows are very important." We're not too sure on this one yet, it mostly depends on how many features the GUI library we are using will get. We hope to have a GUI that is as flexible as possible. "- I see you mention sidechain routing, but it's unclear what are the plans on multichannel audio and, more importantly, the routing possibilities. I'd love to see some kind of node editor for this where you can visualize and manage complex routing schemes for your projects just dragging nodes and noodles." We are currently working on a complex audio graph in the https://github.com/RustyDAW/rusty-daw-audio-graph https://github.com/RustyDAW/rusty-daw-audio-graph repo. This will hopefully allow us to support any kind of complex audio graph structure. So far this audio graph only supports mono and stereo audio, but we can easily add more ports for multichannel audio in the future. Beyond MVP we will likely add either a Live/Bitwig style horizontal rack, or a FL Studio Patcher style plugin for advance routing. It's still being decided on which one we will go with. * edit - fix typo