{"id":1702,"date":"2024-03-29T03:01:38","date_gmt":"2024-03-29T10:01:38","guid":{"rendered":"http:\/\/proxystudio.uxpin.com\/?p=1702"},"modified":"2024-03-29T03:01:53","modified_gmt":"2024-03-29T10:01:53","slug":"should-designers-code","status":"publish","type":"post","link":"https:\/\/www.uxpin.com\/studio\/blog\/should-designers-code\/","title":{"rendered":"Should Designers Code?"},"content":{"rendered":"\n
\"Should<\/figure>\n\n\n\n
<\/div>\n\n\n\n

The argument about how design fits into the workflow of web development is a constant struggle.<\/span><\/p>\n\n\n\n

We often hear designers say, \u201ccan we develop these new onboarding flows and put them into the app?! It will massively improve our conversions.\u201d<\/span><\/p>\n\n\n\n

Then, developers come back with \u201cno. Those onboarding flows are much more complicated than you think, and they use elements we\u2019ve never coded before. I don\u2019t think we should do this.\u201d<\/span><\/p>\n\n\n\n

And that\u2019s just a basic example.<\/span><\/p>\n\n\n\n

Let\u2019s take that situation and scale it up to a team of 20 developers and 5 designers. The result is inconsistencies in design patterns, broken onboarding flows, one week of wasted developer time, slow mobile web-pages, and one date picker that looks like it\u2019s from 1995.<\/span><\/p>\n\n\n\n

Here at UXPin, we\u2019ve seen this situation happen over and over again. <\/span>UXPin with Merge technology<\/span><\/a> <\/span>helps designers build interfaces with coded components from MUI, Ant design, and more. The components look like flat UI components on the surface but they are, in fact, ready for production. <\/span>Try UXPin Merge for free<\/a>.<\/span><\/p>\n\n\n\n

\n
\n
\n

Reach a new level of prototyping<\/p>\n

Design with interactive components coming from your team’s design system.<\/p>\n \n