Lucie Martin

Paris Product Designer @ La Ruche qui dit Oui! Joined almost 7 years ago via an invitation from Etienne S.

  • 1 story
  • 1 comment
  • 17 upvotes
  • Posted to Does UX Design Require Coding When Creating a Prototype?, Aug 16, 2017

    « If the UX designer understands how to write code, then why we need the front-end developers? »« Let the developer do their jobs. »

    In the article, the author seems to confuse knowing how to code and coding like a pro. I’m a product designer and I code. Can I be a real developer? Nope. Do I want to? Nope. Do I believe that learning code makes me a better designer? I do think so. Coding does not only makes you understand better the technical context of your product, it also comes in really handy when you need to test a prototype in specific conditions. I use prototyping tools (Invision, Framer, etc.), but sometimes I need to do more that they can offer. When I need to test a whole flow with real and live data, and I find it better to code the prototype myself.

    « Honestly, users never care about how your function was achieved. » 

    Totally agree. That’s why sometimes I code my prototypes. My prototypes are so bad coded it would make any developer’s eyes bleed. But they work and it is all that matters. Users can test the feature in real condition, and they do not even realize it’s a fake product. They do not have to pretend to be in a user scenario, they just use it like the real product. And the results of those teste are great. My prototype’s code will never be reused when it comes to develop the feature for real, but it was never the point.

    Coding brings you knowledge of your technical context, what’s possible and what’s not, and autonomy in your designer job.

    0 points
Load more comments