Many tools have already emerged in this space in the last 5 years. Some went defunct and disappeared, others are still private beta/alpha or went stagnate altogether, some have been bought out, while others have changed their scope and premise entirely, lastly a few persist. The one thing congruent about all of them is/was the effort to find conciseness of visual and code as to not inundate the user or get in the way of either facet of execution, while seeking to allow each side to derive the same outcome.
The chasm between design and development certainly persists even with so many tools continually trying to bridge the gap. @matjaz mentioned his desire to condense the gap from the design perspective but it was last mentioned close to four years ago. Perhaps it was determined to not be congruent or fit with Pinegrow’s core intentions.
Even so, each aspect has slowly continued to improve in various ways since the initial inception of Pinegrow. From either perspective a person willing to become familiar with the Pinegrow UI/UX can certainly find benefit. Though each of these aspects within Pinegrow can assuredly still be improved further to reduce the burden and improve overall efficiency. However an evident gap will inevitably remain for each groups requirements regardless.
Indeed Pinegrow overall is already uniquely positioned to more adequately bridge this chasm of dichotomy eventually. No easy task however as the divide seems about as old as time itself, with expectations and mindset entrenched on both sides, the struggle rages on.