 So I wasn't ready for this, and I can speak more than five minutes into the subject. So I will go beyond five minutes. I will be told to stop talking. So in the last few days I was hearing you guys talking about developing and doing automatic testing. So I have a background in engineering as well as an engineer. I was wondering when a feature is complete or a task is complete, what does it mean for you guys when it's complete? When the case is resolved, when the functionality is working. This is how I understand it, but it's not. Because yes, I can go to this dialog and then I can open a third dialog and a fourth dialog. And if I use that check mark and then tap OK, yes, it's working. I enter the shape but not. But what about the user? How does he feel about it? Do you even find that feature? So we invest a lot in usability testing or also called UX research. And that's also divided into two. So I'm just unloading information to you very fast. There's a very nice phrase saying never listen to the user when you're talking about usability. And that's completely true. Because if you would go to a person in the street and ask him, will you like that feature? We'll say yes, we will like that feature. So of course, yes, we like all of those features we're talking about. But will they ever use it? So for us, we're doing some research. First of all, identifying the person as the screen guide. First of all, identify the person as the product is for. That specific features are for. And then start doing some servers in the port. And another interesting place to find what users are wanting is the other competitor's forums. We're finally building a text message app. Just for fun. So beyond the MDP of the features of the text message app. I can go to a different, go to WhatsApp or other messengers and see in the forums why people left. What was so bad with the experience or missing feature. And find some cool stuff maybe that could differentiate my app from that. That's one thing. That's for research. What if I already implemented a feature? I build a user flow. I think it's great. The design team think it's great. And engineers implemented it. Everyone is happy QA validated. But it's still, it's a one. But it still doesn't mean that it's working. We use some tools that we can get a video of a user trying to use that feature. And we don't tell them step or her a step to step what to do. And going back to insert an image or a shape. We try to bring the user to an open canvas. Just look at an empty document. And then ask the user insert a shape or manipulate a shape. Without telling them where to tap what to do. Some people will go to the toolbar. Some people will right click to search for the insert option. So it's very, very interesting to see all those flows because you will find a lot of things you could not think of. How a user really use your product. And we're doing so not to validate that our solution was the right one. It's to make sure that the user is able to complete its task. And if our approach did it, then it's great. But we're super aware to the fact that we might get it wrong. So we need to keep improving, improving. And we build a roadmap. We always keep a buffer for improving. And sometimes even pushing features aside. It's not just a check mark to say the feature is complete. You'll always see if it's working. It's very challenging and very interesting. What I like to do a lot is after having maybe summarized all the videos into short clips. And then sit down with the developers and show them back to back like ten very short clips. All the struggle and the pain the user is going through to complete that feature they just implemented. So there's a connection that also I can feel the developers are very engaged. They can feel the pain. Because usually developers themselves are not playing or working with the app. As much as they're working with the code. So that's basically it. One more time, 20 seconds. Yeah. Okay, thank you for listening. We have questions, by the way. Yeah, one question. Yeah, what is it? We, who's we? We, it's me, the product manager and the design team at CloudOm. So the design team, when I say design team is involved with the designers and UX people. CloudOm, we have around five, six designers in-house. We also have externals. When three of them are completely just on the editing tool. The workflow, the finder, we have a lot of tools in our app. One more question? Good. Thank you.