Nutan Bhuva (NK)

Okay. So I'm a designer. Like, my background is, uh, I'm working with the graphic design in 2016, 17. And after that, I speak to the UI designing. And from the 2017 total, I'm working with the UI designer. And from the last, uh, 2 year, I'm going to call setting to some startups and, uh, large skills, uh, enterprises who are building the new softwares. So yeah.

Okay. So, uh, before the 2 year ago I think 2 year ago, like, I'm creating the 1, um, mobile application, uh, for the user user based client. So it's, uh, like, portal sharing mobile applications. So, uh, like, people people can come and, uh, share their home instead, uh, you know, uh, hotel expenses. So yeah. Now in contact case, uh, contact case, uh, like, I'm working with the product designer. I get the end to end flow of the home applications. I'm taking the interview for, you know, uh, people who, uh, frequently traveling on the weekends. So yeah. Uh, this is a high level software.

No. The first first time finding the probing statements, uh, which which, uh, problem we are addressing. Okay. According to I'm prepared, uh, questions. Like, 5 to 6 question is the minimum, but they are dependent on our statement. I'm creating them, uh, more questions. And after that, I'm asking to do you know? 1st, in in between, I'm, uh, finding the right people, like, like, right user, uh, who, like, who can say, uh, our future users. Okay? And uh, and according to him that I'm referring to my research, I'm asking you questions or do like, mister research we are doing is dependent on that.

Uh, actually, it's the same. It's the thing, uh, which is depends on the data, like, which type of data I get. Okay? And, uh, on on on the you know, understand that that data and according to the change the designs. Okay? Like, people are, uh, just for example, like, like, well, like, I enter ecommerce, uh, a few percent people are coming to the, you know, uh, right, the product page. And after they and, uh, you know, like, uh, putting the, um, products into the cart. Okay? That means that we are getting some glitch. Okay? If, uh, they can't really see this, uh, type of, you know, behavior from the user according to that data. Yeah. People are like, uh, 100100 people, uh, 100 user. Uh, they from the 100% I think maybe 80 to 60% of user are coming to the product page, and they are not, uh, putting the, you know, uh, like, uh, things into the card. Okay? So in that case, we are understand maybe we are our placement or, uh, like, our design is, uh, maybe leaking there. Yeah. So it's depending on the data, whichever data we get.

Uh, I've always, uh, dated the people I study is, uh, like, uh, language for the reason. Like, if you are not following the aesthetic, maybe, uh, your design is not looking consistent. So, uh, for that, uh, always, I'm, like, creating the, you know, some, uh, what we should create design language in in my work, you can say. Uh, so which type of color or which type of, uh, like, message we want to, you know, give to the user. And according to, you know, we prefer with the phones and other things. And I'm creating this kit, uh, or you can say a style, uh, to, you know, uh, make consistency on aesthetic.

That's not a tough 1. But, uh, like, UX, I'm always telling the very much here. Like, if you're going to understand the, you know, difference between the UI and UX UX is always a blue blueprint of, uh, in a building. Okay? If you want to, you know, uh, build something in the background, like, if you want to, you know, create, uh, want to build a house, you know, you needed 1 blueprint. The how the structure is going of the, you know, this, uh, home. And based on the blueprint, you create the, you know, entire house. So UX is a blueprint, like, how we are, uh, creating the applications. Okay? What we need on the applications. And UI is a re real example, like, uh, sort of real thing, uh, like designs, okay, plus, uh, style. Okay? So this thing is building the application, which is comes in the real. Okay? So it's a simple way to understand the difference between, uh, UX and UI. And the second thing is, uh, UX is always targeted to users. Okay? Like, uh, if you we are creating the blueprint, we are always, uh, think, uh, how many people are living in this house. Okay? And which type of user they are, uh, you know, using these applications in our test. So and in the UI, maybe, uh, you know, thinking is different. Okay? Like, when when user are come, like, how easily you give, uh, whatever they want. Okay? So just to, you know, think of, uh, UI. Let I thought, uh, make a clear things. Okay? Make up proper hierarchy so they understand the, uh, you know, uh, application. Yeah.

Actually, I didn't get this question. Oh, I don't know. Like, uh, describe your. You take your exam. You do. Hello. Maybe you are asking that, uh, sometime, you know, designs are not not, like, work on doing on technical things, uh, like, with technical things. Like, sometime, you know, you can't do it, uh, with code. Okay? So first of all, you know, I'm used to with, uh, you know, coding languages. Uh, some sometime, 1 of the few time, I'm also running this thing. Not for the, you know, creating the good portfolio, but to to understand the uh, like, which thing I'm creating in the fig in Figma. It's, uh, like, really possible to, you know, creating in the real real life. Okay? If I have something build, which is, uh, non not possible to create in the, uh, and you can say, uh, Flutter or in the interface side, you can set, uh, HTML CSS or with React. So it's, you know, difficult to, you know, redesign everything. So, uh, so I'm used to it that, um, if I'm understanding this question right.

Yeah. As I said before, uh, I'm always telling the story of a civil engineer to, you know, uh, give the concept of UI UX. Like, uh, I'm coming from the, you know, uh, like, small background. Okay? And, uh, like, there, uh, people are just thinking I'm I'm a graphic designer. Okay? But always I'm telling you, I'm a a UX designer. Uh, you can consider I'm a civil engineer. We we're building, like, okay, adding the, you know, entire home, uh, is for the, uh, homeowners requirement. Okay? So in our case, we are creating the applications of, uh, software. You can see website, uh, on the user's requirement or the company's requirement. Okay? So 2 things is happening here. Like, 1 thing is, uh, as per the company requirement, is for the, you know, or director or, uh, CEO's requirement. Right? That's for third reason. But second thing is the user is also including to create the building. Uh, sorry. The applications. Because end of the day, they are using, you know, this, uh, software which which we are building. Okay? So in the in in the if you you know, wearing the head of the civil engineer, they always understand of who people are living in the house. Okay? And, also, they are you know, understand the point of, uh, person who paying him, like, house owner. Okay? So, you know, you always, uh, running on doing on both side and creating the entire house. In our case, we are creating the software. So.

So when you're creating the you know, something which you're, uh, going to the uh, using with with all locations. Okay? So always try to mix something which is common for the old type of user. But when you're creating the something for the local, which, uh, let's say I'm creating a total, uh, which is only using in the USF plus in, uh, users is, uh, you know, like, limited, uh, you know, with a limited h background. So on that time, maybe, uh, like, your job is too easy to understand the user. But in the with the when your application is, uh, using the word while you have to think, like, every type of user, uh, how they behave in your portal.

It's just, hey. I'm I'm used to, you know, working with, uh, this front end designer, and then sometime also doing the. So I know the how, you know, my design is going on the, you know, with the our content designer. So or content developer. Sorry. So yeah. I'm actually used to with that. Uh, I just want to more expensive because, uh, what we can say, Eric, because the the part of the our journey. And, uh, yeah, there's a thing.

Oh, 0, it's not a tough 1, but, but I'm not doing it too much because, as I say, user are, uh, if portal are same, uh, then user are is also same. Right? But, yeah, we can, uh, approach different things when you are creating a mobile application or desktop desktop application. Uh, but is always, uh, like, depending on the research. If you found something which is, you know, if we're creating the mobile app, then going, uh, like, it's good for the, you know, product. And we definitely do. But, uh, in the most of this, we are finding the you know, doing some similarity. So, you know, main when, you know, same user is, uh, like, switching to the desktop to the mobile, they, uh, they didn't get confused. We're now used to with the application. So connection between the desktop and the mobile application, like, as you said, it's it's a need, uh, you know, same other way both thing. But, yeah, sometimes we do it for re really required.