>These are two cultures that are founded on polar opposite ideals and principles.
Designers have a bias in favor of form (brand identity), developers a bias in favor of function (usefulness, productivity). That's why you have those conflicts between devs and designers over the amount of whitespace and functionality within the viewport, and possible results that can be either based on feature overload and bad UX, or that miss crucial functionality.
A way to get both on the same page is information architecture that is informed by generative UX research and positioning. You come up with a content, data model and schema that informs representational and functional parts of your app. Basically a parent discipline for designers and coders within an organization, roles/teams that are made up of designers and coders. This helps to limit the functionality to what you really need, and gives the designers a frame of reference for their prototypes.
Currently, the only thing that designers have shown general interest for is visual coding languages. Unreal engine has Blueprints which probably the most advanced visual coding language out there and in both and 2d graphics visual coding workflows have taken, scripting may have not been so successful but visual coding is definetly something designers so a genuine interest from.Designers tool have become so immensely complex that basic GUI design which usual UX people are accustomed too is no longe enough to satisfy the complexity. Visual coding is here to stay in the designer world and most likely it will leak to the coding world too. For me its the only viable option that I am aware for bring both cultures together.
Designers have a bias in favor of form (brand identity), developers a bias in favor of function (usefulness, productivity). That's why you have those conflicts between devs and designers over the amount of whitespace and functionality within the viewport, and possible results that can be either based on feature overload and bad UX, or that miss crucial functionality.
A way to get both on the same page is information architecture that is informed by generative UX research and positioning. You come up with a content, data model and schema that informs representational and functional parts of your app. Basically a parent discipline for designers and coders within an organization, roles/teams that are made up of designers and coders. This helps to limit the functionality to what you really need, and gives the designers a frame of reference for their prototypes.