Alok Gahlot

So if you talk about my brief introduction, I'm a React Native developer. You guys already know my name. My name is, and I'm a React Native developer with over 3.5 years of experience. During this tenure of my 3.5 years, I have worked with three of the companies. So, the latest one is Invencis Technologies, which is located in Delhi. During this tenure at Invencis, I handled a project named "Map My Customers," which is essentially a CRM application. And in this CRM application, I was responsible for integrating Google Maps. I worked on the Google Places API. I have integrated a color wheel picker and major flows from scratch in this application. Other than that, if I talk about my previous company, which is Zepto. And during my tenure at Zepto, I worked on two of its applications. One is the Zepto consumer application, and the other is the Zepto delivery application. It's an e-commerce application. Both of them are e-commerce applications. And I have to say, if I talk about my roles and responsibilities, I was able to work on the tech stack of React Native, and I have integrated major flows, like the insurance flow, the address flow, even in that, I worked with Google Maps. And I have worked on native modules in Zepto. And while I was at App Inventor, I handled three projects. Two of them were e-commerce applications. One was Adidas, and the other was 6 Street. And the third project that I handled during my tenure at App Inventor was Broker to Broker. So, Broker to Broker is a property trading application where users can sell and trade their properties on the application. I have worked during my tenure at App Inventor on the tech stack of React Native, Redux, TypeScript, and worked on the optimization and integration of RESTful APIs. So, that's all from my experience.

Yeah. Active debugger tools for getting the API calls and debugging the content we are getting from the ABLA. Even I've used the Flipper app and Flipper tool to track the performance of the application, like, how my screen is performing, what FPS I'm getting from the screen currently, and how my data is flowing. And other than that, I've used Reactotron. So Reactotron is also in native apps with other applications, which is helpful to track the state of the Redux, handling and how actions are being passed and projections are called. And other than that, if you talk about professional tools, I've used Firebase and Sentry.

Okay. So rather than passing, it is kind of a static, taking 3 variables for 3 persons. But what if 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 params or adjust all the params before the tax percentage. Like, I will be taking an error or a list of the persons to those who are sitting on the table. And then on the calculation, rather than adding individually, I will be running a map on the list of what I have bought, and we'll be calculating all the total amount while running through and adding all the person's amount. And then I will be calculating the sum on the total amount so that would be scalable. Like, it would be helpful for if any number of persons or customers comes to sit on the table. And, yes, rest, I think, for adding the tip after the percentage. So what I would be getting after the totaling of the calculation of the text plus amount, I will be adding the tip and returning the final result.

Let's play with the storage in the video. And also be different, friendly.

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