 So, Namisha, may I ask you to come on stage? So, I hand over to you the microphone. I will set up your slides here. So, Namisha is our UX hero at NexCloud. And she's, yes, we cannot, absolutely. So, she's going to talk how to make NexCloud more intuitive, useful, and fun by contributing to design. For disclosure, I also have way too many slides, so bear with me, you are my biggest inspiration in how to do like a lightning, lightning talk. There we go. So, I hope I don't get kicked out of the conference. So, yeah. Yeah, hi everyone. So, my name is Namisha and I am the, I work as a UX designer at NexCloud and I also, is this playing by itself? Okay, okay, oh my God, spoilers. Okay, okay, keep at it is. Nice, so, let's start over. Please restart the timer, because this is so stressful. Yeah, so, I'm Namisha. I work as a UX designer at NexCloud and I also started off as a contributor and it was a very enthusiastic contributor at that because when I started contributing, I was still in college and I hung out in every single design call because I didn't want to do my assignments, but clearly I enjoyed contributing to design because I work here now. So, when I first started contributing, I thought that open source was just about coding and programming and coding and programming, but turns out there's way more as we discussed in the panel yesterday. If you haven't watched it, please go watch it again. You can write documentation, you can also do a translation, you can organize events like great audit, you can write blogs, there's so much and since I worked on design, let me show you a little bit about how you can maybe contribute to design. So, let's start small if you see any little paper cuts or design glitches like the alignment is off, we get that a lot, we also point that out a lot so that'll be really helpful if you guys also point out that the alignment is off sometimes. You can just open a little issue about it with maybe a screenshot, it doesn't have to be super complicated, just opening an issue about it can really help get the problem fixed and these are small improvements that have a huge impact when fixed. Also, feel free to include a mockup of maybe what the solution could look like, feel free to go in different directions, these are all the different directions we went in with the new design before we decided on the last one and that can help get some more opinions on what's the nicest looking one. Speaking of mockups, actually, when you're developing a new feature, usability studies can be super useful because, and repeat after me, some things that's obvious to you may not be obvious to everyone else and it's something you really need to understand when you're making a new product as a developer because you're making it for other people who aren't developers. So, how do we do a usability study? Oh, okay. No. Oh yeah, there you go. The order is wrong, but okay. First, you decide on a task. It can be, you know, create a feedback form for your online classes and share it with your students. Then you find someone who has probably not used this software before and you ask them to, you know, do this task and you might see that they're pausing somewhere, they're searching for a button and you note all of these down and, you know, if they ask any questions, note that down as well. And yeah, that's basically it actually. If you do that for just like two to like four more people, you're done and now you have, you know, nice little document with all the pain points that you've really noticed that people are going through when they're using your little flow. Speaking of talking to people, surveys are also something that you can do to get the opinions of what people are gonna find useful. We also had a couple of surveys recently. I don't know if any of you recognize this. But depending on the goal of the survey, designing a survey is like super wide and it's its own thing. So let me just give you some general survey design tips that we try to follow. For example, keep it simple. So people are not gonna answer a question that they don't understand. So don't use technical jargon, keep the language uncomplicated so that people know what your question means. And keep it short. So open-ended answers are tempting to use because it seems like a easy, easy way to get your answers, but most people just don't answer it, open-ended answers. And it's really difficult for you to analyze as well. So maybe you can use a little radio button combination of the most popular answers that you might expect. And third, keep it useful. Don't ask for information that you don't need. For example, we didn't ask for age or gender in any of our surveys because it's just not useful even though it's demographic questions that you can just ask because it's asked in every survey. But we don't really need it. So yeah, you can do surveys. And I think the last one is gap analysis. So gap analysis is basically just a survey of what's happening in the gender area of your product and seeing what your competitors are doing so that you know that you're not developing a feature that no one else has. And people are actually gonna find useful. So in this example, let's go through an example that we literally did for collectives. So the competitors for collectives are like Confluence, Notion, Kota, Etherpad, Krippad, a bunch of stuff. We just selected a few of them. And then you take one of these competitors and see if they have any cool features. For example, Notion has page emojis, header images, table of contents, all nice stuff. And then you note down if anyone else has these things. So clearly, table of contents is the most popular option over here. And then you just keep doing that until you have a bunch of options and boom. Look at that. You know exactly what you need to do to get on par with every other product in the market. So those are some things you can do to contribute to design. You can join us on GitHub using the, you are on GitHub, obviously, we're an open source organization. We also have a design talk, I mean, a public channel where you can pop any small questions you have. And we also have a regular design call at 2 p.m. every Tuesday where you can ask to get your app reviewed. Join us, thank you. Excellent, Namisha. Thank you so much for your talk.