Udemy Course: Complete Web & Mobile Designer in 2023: UI/UX, Figma, + more by Andrei Neagoie & Daniel Schifano.
Episode 22: Where To Go From Here
Introduction
After all that hard work, you finally showed your designs to Bruno at Habitual. Does Bruno like it? Well, Bruno loves it. He has been so inspired by your design work.
Bruno: Hurray! Good job getting this far in the course.🎊
Project Handoff
The diagram below illustrates an endless cycle from; Ideas > Planning > Design > Development > Launch.
We have just completed our planning and design phase. We've taken on the role of a designer and have created a product. But now, we have a critical part, which is the handoff to the development team.
Usually, you hand off your designs to developers, so that they can build the product and launch.
So how do things go as a Designer, when you work with developers? Let's find out.
Working with a Developer
The traditional way that designers would work with developers was in what we call a "Silo".
i.e
A Designer would just work by themselves and then once they're done, they just hand off the designs to a developer. And the developer just had to create this pixel-perfect product based on those designs.
Now, this process isn't always the best, mainly because there's a lack of communication between developers and designers. In this scenario, ideas can't be shared. Maybe the designer is the only one who talks to the client and the developer has no idea what the client wants.
So, it is more common to see designers work much more collaboratively with developers working in teams, maybe with; product managers, and scrum masters, so that everybody works together to complete this cycle that we see here.
And we always have this post-launch phase where we have to iterate and learn to constantly improve the product.
For a developer, it is really hard to go from design to actually building the product, using something like a programming language. At the same time, a designer might wonder why this developer can't do something that they have designed, or why this developer created something different or slightly different from what they designed
So, the key to a successful designer-developer handoff is, as a designer to always keep the developer(s) in mind. This is why it is good to:
communicate with the developer(s) and design things based on what can technically be done.
design effectively for the platform you're building in.
A developer should know enough about design theory to collaborate and have a mutual language that both(the developer and designer) can speak together. The idea of mutual understanding and respect is the key to collaboration because, at the end of the day, you're working to solve a problem for a user.
So as a designer, by learning what a developer has to do, you're going to be a lot better at communicating with developers and vice-versa.
This is why we have upcoming sections in the course that cover some basic programming/coding knowledge like; how HTML & CSS work and how you might be able to put a website online, so that when you work closely with a developer as you should, you're able to understand what they do, how they work, but also gives you that flexibility to potentially build your products, by being your own designer and developer.
Now, my course instructor (Mr. Daniel Schifano) loves this quote but he is not sure who said it:
"Always design/code as if the person who ends up maintaining your work will be a violent psychopath who knows where you live."
This implies that it is important to think about who you're working with and who you're designing for; so that everybody ends up happy.
So, in the next couple of Episodes, we will be looking into the web development world.
The journey gets better 💪...
#Figma #ProductDesign #UIUXDesign #UIUX #UIUXCourse #Branding #BrandStrategy #UIElement #Design #Motion #MobileApp #WhereToGoFromHere #Udemy #UdemyCourses #ZTM #ZeroToMastery #DocumentingMyTechJourney #BuildingMySkillset #TechSkill #SkillSets #ProductDesigner #EngrShege #ES