Nutan Bhuva (NK)

My background is in graphic design, specifically in 2016 and 2017. After that, I transitioned to UI design. Since 2017, I've been working as a UI designer. From the last two years, I've been consulting with startups and large enterprises that are building new software.

Before two years ago, I was creating a mobile application for a user-based client. It was a portal sharing mobile application where people can come and share their home instead of incurring hotel expenses. In the case of contact, I worked with a product designer to get the end-to-end flow of the home application. I conducted interviews with people who frequently travel on weekends. This is a high-level software.

The first time finding the probing statements, which identifies the problem we are addressing. Okay. According to my preparation, the questions. Like, five to six questions is the minimum, but they are dependent on our statement. I'm creating more questions. And after that, I'm asking: Do you know? First, in between, I'm finding the right people, like the right user, who can say our future users. Okay? And according to him, referring to my research, I'm asking questions or does the research we're doing depend on that.

Actually, it's the same. It's the thing which depends on the data, like, which type of data I get. And on understanding that data and according to the change the designs. Like, people are just an example. I enter ecommerce, a few percent of people are coming to the product page. And after they put products into the cart, we're getting some glitch. If they can't really see this type of behavior from the user according to that data, yeah. People are like 100 out of 100 users. From 100%, I think maybe 80 to 60% of users are coming to the product page, and they're not putting things into the cart. So in that case, we understand maybe our placement or our design is leaking there. Yeah. It's depending on the data, whichever data we get.

I've always dated people I study language for the reason. If you're not following the aesthetic, your design may not look consistent. So, for that, I'm always creating some design language in my work, which you can say is a set of rules. This includes determining the type of color or message we want to give to the user, and taking into account how people interact with phones and other devices. And I'm creating this kit or style guide to make consistency in the aesthetic.

That's not a tough 1. But, like, UX, I'm always telling the very much here. Like, if you're going to understand the difference between UI and UX is always a blue blueprint of a building. Okay? If you want to build something in the background, like if you want to create a house, you need one blueprint to determine the structure of the home. And based on the blueprint, you create the entire house. So UX is a blueprint for creating applications, defining what we need on the applications. And UI is a real example, a design, plus style. So this is building the application, which is what comes in the real world. So it's a simple way to understand the difference between UX and UI. And the second thing is, UX is always targeted to users. Like, if we're creating a blueprint, we're always thinking about how many people are living in the house and what type of user they are, which we use in our tests. So, in UI, the thinking is different. Like, when users come, how easily you can give them what they want. So just think of UI as making a clear hierarchy so users understand the application.

I didn't get this question. Oh, I don't know. To describe your experience, you take your exam. You do. Hello. Maybe you're asking if, sometimes, designs aren't like working on technical things, with technical things. Sometimes, you can't do it with code. Okay? So first of all, I'm used to working with coding languages. Some of the few times, I'm also running this thing. Not for creating a good portfolio, but to understand which thing I'm creating in Figma. It's really possible to create in real life. Okay? If I have something built, which is not possible to create in, say, Flutter or the interface side, you can use HTML, CSS, or React. So it's difficult to redesign everything. So, if I'm understanding this question right.

As I said before, I'm always telling the story of a civil engineer to give the concept of UI UX. Like, I'm coming from a small background. And, there, people are just thinking I'm a graphic designer. But always I'm telling you, I'm a UX designer. You can consider me a civil engineer. We build, like, an entire home, okay, based on the homeowners' requirement. So in our case, we create software applications. You can see a website based on the user's or company's requirement. Two things are happening here. One thing is, as per the company requirement, for the director or CEO's requirement. That's the first reason. But the second thing is the user is also involved in creating the application. Because at the end of the day, they're using the software we're building. Okay? So, wearing the head of a civil engineer, they understand who the people are living in the house. And, they understand the point of view of the person who pays the house owner. Okay? So, you're always running on both sides and creating the entire house. In our case, we're creating the software. So.

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

I'm used to working with a front-end designer, and sometimes also doing the design. So I know how my design is going to go with our content designer, or content developer. Sorry. So yeah, I'm actually used to that. I just want to make it more expensive because, what we can say, Eric, because this is a part of our journey. And, there's a thing.

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