Application of UX Design in a Developers World
If users don't love the experience, your code goes nowhere
Long before a line of code is written, the design should already exist on paper. If users are not finding and loving the experience, a project cannot move from one point to the next, however solid the code behind it. Software developer and She Code Africa chapter lead Ofonime Brown asks what changes when a developer starts thinking like a UX designer.
Learn a simple recipe for bringing UX thinking into every stage of your development work
In short
Ofonime Brown, a software developer at Beasiz, argues that developers should build with the eye of a UX designer rather than jumping straight into code. She offers a simple developer's recipe (usefulness, durability and artistry), urges thinking about the user before, during and after design, and recommends checking back with users and working alongside UX designers.
“But before you can build in that codes, why not think of the design that you want to work with?”
“You know, you have to think like the UX person.”
What you will learn
- Plan the design and know your target customers before you start writing code.
- Apply a developer's recipe of usefulness, durability and artistry when shaping a project.
- Sketch and code on paper first, then move the work to your laptop.
- Think about the user experience before, during and after design, including the project's future.
- Validate your work by returning to the drawing table and asking users what they need.
Key takeaways from the speaker
- !. A developer must have the eye of UX design.
- 2. UX Design must be an essential in the life of a developer even if it's in parts.
- 3. Ux design is simplified
Details
- Level
- Beginner
- Format
- Talk
- Technical depth
- Introductory technical
- For
- Student, Early career
- Length
- 11:58
- Published
- June 2021
Questions this talk answers
Why should a developer care about UX design?
Brown says that if users are not finding and loving the experience, a project cannot move forward, so developers need the eye of a UX designer.
What should a developer do before writing code?
Think of the design you want to work with, know your target customers, and sketch or code it on paper first.
What is the developer's recipe?
Brown compares it to cake ingredients: ask why the project is useful, how to make it durable for clients, and how to make it artistic so it stands the test of time.
What should happen after a design is built?
Go back to the drawing table, keep checking, and ask people what they need, because they will tell you.
How can a developer learn to apply design thinking?
Work alongside UX designers, observe how they start projects and the quality of their work, and relate it to your own role.
About this talk
I will be describing ux design as an essential part of a developer 's process as we build a project.
Topics
Highlights
- Think design before you write code (72 s)
- Code on paper and the developer's recipe (74 s)
- Before, during, after, then check again (37 s)
Speaker 1: Good morning, everyone. Hello, my name is Brown Ofonime. I'll be presenting on UX design in the developer's world. How to apply your UX design, how to as a developer, as working in a developer's world. You will like to. Apply the design into the system. That you won't even have any issues when people are asking you what kind of what kind of software did you build? But if you can just you can if you can see your build to work your project as in the design high, you will not have issues building anything for anybody anywhere in the world. So first and foremost, I'm.
Speaker 1: From. Speaker 1: Um, this screen. Um, so, so I'll be able to talk better because I have, I think I have just 15. 12 to shoot a finish up. Speaker 1: So design is a plan like, and it's, um, it's registered. It's, it's, it's, it's, it's traced back to the ancient Romans where everything was built for perfection and.
Speaker 1: And it's. And so we can also know that if you go to the Romans world, all that DZ, all that design with you. Speaker 1: That we are even in trying to incorporate now into our home system anywhere in the world in Africa, Asia, anywhere. Speaker 1: Anywhere. And also we also know that some UX design. It's, um, a user experience design.
Speaker 1: And if the user are not experiencing the design, if they are not finding it, I think they're not loving it. Speaker 1: There's no way you can move from that from one point to the other part of your work. Speaker 1: And I'm, I'm not going to be talking about UI designs. Now just focus on the UX design, the user experience design.
Speaker 1: And you know, um, like the quotes that I always like to, um, use when I'm. Speaker 1: That perfection. Speaker 1: And there's nothing left to take away, you know, when you are doing your design and as a software, you know, we are always concentrating on building in the items, um, codes into the design. Speaker 1: But before you can build in that codes, why not think of the design that you want to work with?
Speaker 1: You know, you can work with the, um, let's say in UX design and you guys can develop something together, but you have to be in perfection to that perfect. Speaker 1: You are trying to work out and UX, UX have different, um, UX design always build different kind of customers in large quantity in large quality.
Speaker 1: Depending on what you're trying to thinking of the future of where you want your design to end up or where you want your project to be. Speaker 1: So you all, you must always think of that first and foremost, and you know, you should also know the target customers, your clients, when you're talking about your designs whatsoever.
Speaker 1: So when we are talking about designs, we have different types of design, but we'll be focusing on the software designs. Speaker 1: It's actually the process by which an agent or a customer or a client creates a specification of a software artifacts intended to accomplish goals. Speaker 1: And you know, in designs, you must always get goals as a software developer.
Speaker 1: You must always let your goals align with the design that you're trying to be. Speaker 1: If your goals are aligned in the goals of. Speaker 1: Well, as a person, you will not be able to make the design come alive. Speaker 1: And people out there will not be able to pick out the. Speaker 1: This is actually what you were trying to do.
Speaker 1: And you know, like this picture. Speaker 1: In this session here. Speaker 1: It's actually. Speaker 1: When you look at it, you know, there are two pictures inside this design, but when you look at it as a. Speaker 1: You'll be able to like I don't like this design. Speaker 1: I want something better than this.
Speaker 1: And as a software developer, if you add the eye of the UX design, you know, some people actually have a very good for a very good eye for design. Speaker 1: So by the time you look at it and you're like, okay, I can actually code something to be like this. Speaker 1: You can actually build it, but it has to be.
Speaker 1: Of the UX design. Speaker 1: Now. Speaker 1: UX. Speaker 1: In fact. Speaker 1: Process when teams used to create products that provide meaningful and relevant experience to users. Speaker 1: This involves. Speaker 1: Process of acquiring. Speaker 1: I think it's a product. Speaker 1: The aspect of branding. Speaker 1: It can also be.
Speaker 1: Usability functionality. Speaker 1: You can actually think of your design as if. Speaker 1: Whatever or whatever projects you are trying to build and as a software developer, how do you like the design into code by time you see it, you know, first do it on paper. Speaker 1: First code on paper first, then transfer the codes into your into your laptop and before you know it.
Speaker 1: Be actually like exercise, but but because you're not a UX design software developer, you'll be creating amazing designs for people such that people be in hate of what you're actually doing and you actually look out for you more than the other developers. Speaker 1: So the developers. Speaker 1: I like calling it developers recipe is like an ingredient when you're trying to make a cake, you know, the usefulness.
Speaker 1: Why do you want to make it? Speaker 1: Why do you want to build this project? Speaker 1: Why do you want to use this particular design? Speaker 1: You know, the durability. Speaker 1: Why do you actually want to make durable for the pro for the client or for the for your customers? Speaker 1: You know, you have to think like the UX person.
Speaker 1: Then how do you want to be artistic of I'm like, I mentioned the Romans people in the olden days the what they were trying to build the team standing the test of right now. Speaker 1: There's no way that the ancient Romans kingdom that you know, like I love this. Speaker 1: It was old because of the recipe they put into the plan, the progress, the the functionality of everything that.
Speaker 1: So think of what you know that you can actually build, you know, the beginning is always the others, but you can actually actually check out something. Speaker 1: Write it down on paper for us, build it out on paper for us, you know, sits with a UX design. Speaker 1: So by the time you sit up together to make a particular project, you'll be thinking design and you'll be building like a UX design.
Speaker 1: Now I'm going to be showing you some pictures where you can actually decode a UX designer. Speaker 1: If a UX designer sees this, this is a combination of pictures. Speaker 1: But for a developer, the developer might just pick just one picture on that and build on that. Speaker 1: But as a UX designer, you can actually think of how to think, put everything together and build on whatever you want to build.
Speaker 1: Depending on your usability, your durability, your durability, which is the future terms of what you're building for now. Speaker 1: So like you see this. Speaker 1: Different pictures put together. Speaker 1: By a designer. Speaker 1: But as a developer, we've been trying to build something that will be applying to the UX world is is going to be different.
Speaker 1: So please think of this picture. Speaker 1: Then now I had to use this recipe. Speaker 1: Well, when you are developing as a developer, I am thinking. Speaker 1: The before design must be put in place during the design. Speaker 1: And what's the experience, what is the experience you want the users through during the design and design.
Speaker 1: Whatever you think your. Speaker 1: Clients or customers will be trying to buy from you. Speaker 1: So what is the future of that of that project that you're trying to build? Speaker 1: You must always think of that first. Speaker 1: Design is actually a broad stream of subjects is not limited to design is not limited to software.
Speaker 1: And it's not also limited from architect or different, but we can see it in different stages now, different departments. Speaker 1: Different schools. Speaker 1: Actually related roles that which exists in a range of departments in everywhere. Speaker 1: And you must actually see something that will catch your eye and by the time you know it, you are able to replicate that same design or even do something better than that.
Speaker 1: So when you are thinking of designing in the as a developer, think of it as a designer. Speaker 1: Think of the before the during the design and after those three things must be put in place for you. Speaker 1: Achieve what you want to do in your goals. Speaker 1: Now, after all. Speaker 1: What next?
Speaker 1: Again, check again. Speaker 1: Go back to the drawing table. Speaker 1: Check again. Speaker 1: Keep on checking. Speaker 1: Ask questions. Speaker 1: Ask people. Speaker 1: What do you need to do? Speaker 1: Ask them. Speaker 1: They will definitely tell you what you need to do. Speaker 1: So I'll just be, I think I have like three minutes more.
Speaker 1: This is me. Speaker 1: My name is Brown Offenime. Speaker 1: And if you want to reach out to me, there is the link that you can actually reach out to me at Linus Brown at Gmail. Speaker 1: Then you can also connect with me. Speaker 1: As Linus Emae Brown on LinkedIn. Speaker 1: Thank you for your time.
Speaker 1: Let me check if I have questions so that we can actually talk about the questions. Speaker 1: Any questions there? Speaker 1: And you apply the design to the role of a developer. Speaker 1: Good. Speaker 1: Like I said before, how to apply the role of the design to the role of a developer. Speaker 1: You think like them.
Speaker 1: By the time you see if you have a UX design, you can work with them. Speaker 1: You know, by the time you are working with them, before you know it, you'll see different things that they are doing. Speaker 1: And you also see the quality of their work, what they are trying to build, how they go about starting the project.
Speaker 1: And you will be related to you, to your role too. Speaker 1: Okay. Speaker 1: So thank you. Speaker 1: Thank you, Rebecca. Speaker 1: Thank you, Ruta. Speaker 1: Thank you, everyone. Speaker 1: I think my time is up. Speaker 1: So you can connect with me on LinkedIn. Speaker 1: Take care. Speaker 1: Bye.
Transcribed automatically; names checked against the speaker record. Select a time to jump there.
Frameworks and ideas mentioned
- Developer's recipe (usefulness, durability, artistry)
- Before, during and after design
Cite this talk
Ofonime Brown. "Application of UX Design in a Developers World." WomenTech Network, 2021. https://www.womentech.net/video/application-ux-design-in-developers-world
Related talks
Browse the libraryDesigning the Future: A Journey into the Revolutionary UX of the Mercedes Vision AVTR
Mercedes wants the car to reach out to you, not the other way round
Usability Testing - short and simple
Why 'we know our users' is the best reason to run a usability test
An Introduction to Building Apps for the Modern World
Jetpack Compose and SwiftUI are closer than most beginners think
Age and Interface: Equipping Older Adults with Technological Tools
Technophobia keeps many older adults offline, and interface design can help
Co–navigating the changes in healthcare
Ask clinicians what they want and you mostly get incremental answers
When Can We Ship?? A Fun Exercise in Estimating Software Tasks
A 6.5-hour paint job turns into 14.5 hours once you ask the right questions