Tejas Sagathia

Would you help me to understand more about your background by giving a brief introduction of yourself? Hi. My name is Tejas. I have to tell you, uh, this is, uh, And, uh, I have worked, uh, mainly apps like business app, finance app, survey app, medical app. Okay. I'm giving the introduction about all this app. In business app, uh, in business app, user can, uh, user, uh, it is about the farmer and, uh, uh, pollinations. Okay? Beekeepers and farmers, uh, in a beekeepers can upload the data about the honeybee honeybee, and, uh, farmer can get the department of the, uh, honey bee honey bee from the honey bee, beekeepers. Okay. So farmers and, uh, Beekeepers can communicate which feature that through this, uh, business application. I will integrate into the check functionality, the app native. You can check as and, uh, both the farmer and beekeeper can communicate with each other and, uh, generate the contract. So this is one type of the business application. I also, uh, worked in, uh, in in learning application in learning applications, uh, teachers can upload the assignments in a video format, in audio format, in, uh, in PDF format, Excel format. Uh, student can also log in and get this type of uh, assignment uploaded by the teachers. K. Teacher can also conduct the online exam, uh, like, uh, so user can user can attend the online exam, and, uh, user teachers can also get the attendance of the exam and the student also. So in in, uh, e learning applications, uh, there are 3 or 4 users. Uh, student can also log in there. So teacher can also log in there. Principal can also log in there. So who can help Edwin Edwin can also log in there. So e learning app is very, uh, most of very, uh, MS and IO integrated to mini upload functionality and the audio and video functionality in the elearning app.

Can you outline a method for statement when a is compared with the both end of the NASH? Yes. Uh, in, uh, in React Native has a mini statement in metal like MobX, uh, Redux. Context context is inbuilt in React Native, so don't have to install the any third party library. In our context, there is, uh, one provider. We have to get the application with the provider, and we have to input the value. We can insert and get the value from the use context. So So using, uh, using the context API, we can, uh, we can centrally manage this step. Uh, there is also one, uh, high leptomous, uh, deducts. Deductions is very used in, uh, many applications. Redux is Redux has, uh, many, uh, deduct has the actions, reducers, and, uh, store. K? Store, we have to wrap our application with the store. Okay. Uh, but we can, uh, get the, we get get the, uh, updated state from the user, use selector, and we can hold the actions, uh, using the user dispatcher. Uh, uh, action is a one type of JavaScript object. We can pass the type and the, payload property. Uh, so, uh, XR is passed to the reducer, and a reducer will pass pass the updated state to the store. And the store will, uh, store will, uh, pass the app updated app to the, uh, whole, uh, whole app. So, uh, main main parameter we can say that Redux is the actions, reducers, action reducer store. K. Uh, and, uh, we can get the updated state using the useDispatch hook, uh, and the, uh, you select the. This is for the state management.

To pull the RESTful API, One of the best, uh, third party API is Axios. We can pull the SQL API through the, uh, Axios Axios, and, uh, we have to serialize enter the serialization and deserialization of the next type object in React Native. So, uh, using the, we have to call the API, and, uh, we we can get the restful response from the a from the Axios as well as page. But page is, uh, integrated in the JavaScript and the dev native. We don't have to install the, uh, install the 3rd party library. But, uh, Xeos is advanced, so we can use the Xeos. So we can use the Axios for the dashboard API. We can insert the required API URL headers, uh, and the, uh, requires authorization, and we can get the, uh, response. And, uh, you need serial adjacent and desalination of the test type object in React Native. And we can get the nested object in the, uh, React Native. So we can, uh, first apply the, uh, we apply the response of the test pool API to 1, uh, one variable. We can pass this response to the one f variable, and we can get the, uh, nested object through load here in the RESTful API. Uh, for example, uh, we can we can uh, apply we can, uh, declare variable rest, and we can call the API and pass this we can pass this response to this, uh, rest available, and we have some nested object like, uh, dot data dot dot data dot response dot error. Okay. So we can get the nest, uh, nested object through, uh, data dot response dot error. So, like, uh, likewise, we can get the get out the serialization, deserialization of the nested object.

How do you manage dependency conflict when upgrading React Native and its lab ready? Dependency conflict mind upgrading library. So, uh, first of all, uh, we have to apply 1, uh, command. I have told react native upgrade. When we apply this command, react native upgrade. Okay. So it will check the current version of the React Native. It will, uh, first, uh, check all the version of the dependency of and, uh, start the upgrading. We can also upgrade the React Native 1 by 1. Yeah. Like, if if my current React Native version is 0.60, so we can up update the React Native version 1 by 1 while, likewise, 0.61, 0.62, 0.603. We can directly update 1 reactivity version to the other reactivity version also. And it is advisable to that we can upgrade the react native, uh, version 1 by 1. So, uh, first of all, when we apply the command React Native upgrade, that time we have to check check for which dependency is make, uh, made is creating error or creating conflict currently. So we have to check which version is is applicable this to this, uh, the active version. So we have to apply that version, and we have to start upgrading. So 1 by 1, we have to check which dependency is making conflict and, uh, which is the version for which the dependency version is suitable for this current version. And, uh, so 1 by 1, we have to check. 1 by 1, we have to upgrade the dependency version in 1, uh, and try and error try and try error and start troubleshooting. We have to upgrade the the creative version as well as the creative dependency in taken to JSON file.

How would you implement a picture toggle system in the negative word cross platform app? How would you implement a picture The question is, how would you implement a picture toggle system in the for a cross platform here? So I I can't get the exact idea about the toggle system. Which which type of toggle system are you talking about? So I cannot give the exact answer of this, uh, questions, but I I will try. If you want to, uh, if we want to apply a toggle system, So we can apply the toggle system using the using the hook. We can apply we can, uh, apply the toggle system using the hook. Likewise, uh, using the hook, we can toggle the variables and as well as the toggle the variables, we can toggle the UI. Okay? Uh, we can toggle the, uh, variables using, uh, use state of if state is positive, we can make it negative. If, uh, if, uh, state is negative, we can make it positive. So using the toggle system of the hook in variable, we can, uh, toggle the UI. K? And we can make the one toggle system in the toggle feature in the React Native. So I I can't get the exact idea about which type of toggle system you are talking about. So I am just giving the, uh, answer is for the my my understanding. K. So we can make the toggle system, like, uh, using this using this using the user token, and we can toggle the variables. And, uh, using this value object variable, we can toggle the system.

I have checked this, uh, concern. I have not found any error on both that can lead by API. I call it this, uh, function. But, uh, I have noticed the one console dot error. As per my point of view, we can. It is, uh, advisable to use console dot log rather than the console dot error because, uh, sometimes console dot error is creating issue in the applications. It is creating some some issue console dot error. So there is no any any problem better than console dot error. So I I will give only one remark on this, uh, concern that it is advisable to use console dot log data then console dot error in application. Okay. So we can get the required log of the error. It will not create the, uh, error in future console dot error. So this, uh, function is good. Just, uh, use the console dot log rather than console dot error.

Use the arrow function when you are updating the state, which depends on the previous output. So, uh, here, we are not using the the arrow function. So use the error function when you are updating the current value using the previous input. Sometimes state is not updated. It can trigger the error.

Describe a strategy to manage and apply state updates across the multiple in media. We have told data, uh, for state management is Redux and some Webex, and so it's kinda, uh, context API. Yeah. Context API is inbuilt to the. So we can, uh, pass the main component in the provider. We have to pass pass pass the main component in the provider, context provider, and we can, uh, get the updated state using the use use context API. So we can use the context API, and we we can also use the Redux. Redux is very popular. In Redux, there is XAN in the user store. XAN is 1, uh, JavaScript object, which have the type and payload property. Uh, we can pass these, uh, actions. Uh, we can, uh, hold the action using the user dispatcher. Uh, We're able to pass it action in the we have to pass this action in the reducer. Reducer will update the state, and we have to pass the many reducer to the store. And, uh, we have to pass this updated store and the provider. And using the store, we can pass the updated state in the old components of the app. So using redux, like, uh, access, reducer, and store. We can update the step, and we can pass the updated step to the old components of the app.

If we want to give the constituent law of the UI in all devices, so first of all, we can give the percentage wise width and height. Okay. If we are giving the percentage wise width and height, it will calculate the current devices, width and height. Uh, according to that percentage, it will give the required output. We can also we can also we can also count the width and height using the, uh, sigma difference width and height, sigma reference component we can write in current device, we can compare if, uh, in Figma, which is, uh, which is, uh, 240 and current device ID is, uh, 750. So we have to calculate the, uh, calculate the current devices component height and width. According to that, we can give the value. So it will react as per the device's height and width. It will not break any UI. So it is advisable there. If we are using sometimes image, we can also use the pixel ratio. If we are showing the image using the pixel ratio, it will not stretch. So using, uh, we can also use the pixel. Let's see. We can also use the, uh, scale size. Scale size using the Corona devices and height and, uh, Figma and devices. And we can view the height, and we can also view the percentage by.

How would you architect your identity application for scalability with thousands of current users. 40 thousands of concurrent users. I have no more idea about this scalability, but, uh, it is advisable that if, uh, we have the thousands of the concurrent users, so it is advisable that to write a clean code. There should not be any infinite loop in the code. If, uh, any infinite loop, it can create the problem to the users. So ports should be clearly, and we have some some good good. We can, uh, clean all the all the variables in return statement of the use step. So if we write clean all the code, all the variables, all the state, clean all the state in the return statement of the user app, So whenever the component is unmounted, that that variable will be will be released. So it it it will not, uh, creating any issue any issue of the memory management. Okay? So when we have we want to architect a scalability for the VXNETI application with the 1,000 of the phone current users. So we can write a claim for it. We can, uh, release the applicator release the memory in the, uh, return statement of the use state, we can, uh, make sure that we are not calling the API continuously. If, uh, we can also use the some, uh, inbuilt concern of the use memo, use use memo. And use use memo Because, uh, we use memo is one type of that it will, uh, compare the current output to the previous output. If state is not updated, it will not re render the UI. So we can take, uh, many many. We can, uh, we can make one good habit to your mouth key component in the use memo so that memo so that, uh, it will not read under unnecessarily. So we can increase the stability of the app when we are using thousands of different users.

I have not used the the mode jack for testing, so I cannot give more information about it. Sorry for that.