Bent from Fuse here — that's indeed our primary design goal. We believe designers shouldn't necessarily learn to code, and coders shouldn't be fluent in design, but getting each role to come close together and to give them a common language and similar semantics, as well as a platform that enables quick iterations, is important to us.
Our CEO (and primary engine coder) was interviewed by Forbes earlier this year, and in the interview he touches on A LOT of these points: https://www.forbes.com/sites/julianmitchell/2017/06/29/this-...
Quick quote:
"Our (former) jobs as programmers at ARM gave us a front-row view of all the capabilities of modern mobile devices, and it became apparent that most developers underutilized a lot of these devices. As a consequence, much of the raw power didn't benefit the end users who bought these pocket-sized supercomputers. Secondly, the way apps are developed hasn't changed much in the last 20-30 years. New tools and computer languages have come and gone, but the process remains largely the same, with developers and designers operating in separate worlds, using a different set of tools.
This is partly because collaboration across these boundaries requires a huge amount of additional work just to translate and re-implement the vision of stakeholders and designers into production code. In turn, this resulted in unsustainable processes of slow iterations for testing and validating ideas. Consequently, you end up with products and user experiences that are less thought-through or polished, even though you've spent an unacceptable amount of time, resources and risk to produce them.
These two takeaways lead us to realize that what was needed wasn’t another micro-optimization tool. We had to take a step back and consider the entire development process from through the lens of product owners and designers, as well as developers. Fuse is the byproduct of that process."
