Alok Gahlot

Okay. So if I talk about my brief introduction, I'm a React Native developer. Developer. You guys already know my name. My name is, and I'm a React Native developer with our experience of 3.5 years. During this tenure of my 3.5 years, I have worked with 3 of the companies. So latest one is, uh, Invencis Technologies that is located in Delhi. During this, uh, tenure in, uh, Invensys, I have handled a project named map my customers, which is an basically a CRM application. And in this CRM application, I was responsible to integrate Google Maps. I have worked on the Google leads API. I have integrated color wheel picker, and I have integrated major flows from the very scratch in this application. Other than that, if I talk about my previous company, that is Zepto. And during the tenure in Zepto, I have worked, uh, I was I was responsible of handling 2 of its application. 1 is Zepto consumer application, and the other one is Zepto, uh, delivery application. And it is an ecommerce application. Both of them is an ecommerce application. And I have, uh, if I talk about my roles and responsibility, I was able, uh, I was working on the text tech of React Native, and I have, uh, integrated there also the major flows, like the insurance flow, the address flow, even, uh, in that also, I have worked in the Google Map, uh, Google Maps. And even I have worked on the native modules in Zapco. And while I was in App Inventor, I have handled 3 of the projects. 2 of them are the, uh, 2 of them are of ecommerce application. 1 is Adidas, other one is 6 straight. And, uh, the 3rd project which I have handled in during the tenure of App Inventive was broker to broker. So broker to broker is in a property trading application where user can sell and, uh, trade its, uh, sell and lease its property on the application. So, uh, I have worked, uh, during the tenure of App Inventive, I have worked on the tech stack of React Native Redux, TypeScript, and, uh, worked on the optimization and integration of the restful APIs. So that's all from my

Yeah. Active debugger tools for, uh, getting the API calls and to debug the about the, uh, content, what we are getting from the ABLA. Even I have used the flipper app flipper tool to track the, uh, track the performance of the application, like, how my screen is performing, what f FPS I am getting from the screen currently, and, uh, how my data is flowing. And other than that, I have used Reacttotron. So Reacttotron is also in other, uh, the native g v with other application, uh, which is, uh, helpful to track what are the states the state of the Redux is, uh, handling and how the actions are being, uh, passing and projection is called. And other than that, if you talk about the professional tools, so I have used Firebase and, uh, Sentry.

Okay. So rather than passing, like, it is kind of a static, uh, taking 3 variables for 3 persons. But what if, uh, they are only 2 persons or they are more than 3 persons on the table? So what I will do is, firstly, I will change the, uh, params or beef all the params before the tax percentage. Like, I will be taking an error or, uh, I will be taking an error or a list of the person to those who are sitting on the table. And then on the, uh, then on the calculation rather than, uh, adding individually, I will be running a map on the, uh, on the list what I have bought, and we'll be calculating all the total amount while running the while adding all the uh, person's amount. And then I will be calculating on, uh, calculating the sum on the total amount so that would be scalable. Like, it would be helpful for if any number of, uh, person or customers comes to sit on the table. And, yes, rest, I think, for adding the tip, uh, after the percentage. So what I would be getting after the, like, totaling of the, uh, after calculation of the text plus amount, I will be adding the tip and returning the final directly.

Let's play async the storage in the video. And also different, uh, friendly.

Shit. Uh, sorry. I mistakenly I have uploaded the previous video of the storage. So I'm covering both the answers in this. So in the storage, like, storage is the, uh, local memory storage where we can save the data in of React Native inside the, uh, inside of a local memory. So, uh, we can use async storage when we are not using the Redux kind of thing. Like, async storage will be help to store in the, uh, help to store in our local memory. So now let's on moving on to this, what is prop drilling. So prop drilling is basically if we are having 4 components, 1 a, b, c, d, and we have a prop named a. But we have to pass that prop on-site, uh, onto the component d level. So what we're doing from, uh, we are passing our prop from a to b. Then we are passing that same prop from b to c. Then we are passing that same prop from c to d. Then, uh, like, the prop passing from b to b and c are kind of useless. Less, uh, they don't require that prop. Only the prop was mentioned in, uh, the property was originally mentioned in a and required by, uh, component d. So b and c are, uh, uselessly calling that prop. So that is what prop drilling like, from moving top to bottom in a component without passing the same property or prop that is prop drilling. So we can avoid the prop drilling by using context API. Like, we can create a context from, uh, of, uh, like, in context API, what we have is we have a consumer and we have a provider. So a will be become as a provider, and d will be become as a consumer. So, directly, we can pass the, pass the context from a to d, and, uh, they can, uh, fetch that context and get the property that is being passed from, uh, that is being provided from a inside the context. And other than that, we can use Redux directly. So we can, uh, hold that property in the Redux. Redux is a global space that can be used any, uh, across the screens. Uh, like, uh, it is a central centralized store, so any screen can fit that store from, uh, anywhere. So these are the 2 ways we can avoid properly.