Ankur Thumar

Yes. Myself, Ankur Kumar. I have total 5.5, uh, 5 years of experience in iOS. Uh, in my career, I have worked with many various clients That's, uh, in the ecommerce platforms. It's, um, for the gaming platform as well as for the new features like audio call, video call, socketing, clean number sense. I have completed more than 20 plus applications in that. Uh, also, I have uploaded on that app store. And also, I have reviewed on that.

Yes. Uh, for the technique, I have applied for the network layer exception in iOS. I have, uh, I have used the various, uh, like, alarm of fire and as well as, uh, the core native URL sessions. For the alarm of fire, we have used AF methods, and that, uh, usually, uh, call, uh, get and post a method for, um, to get the response from the APIs. And for the, uh, URL session, it will build on the task, and, uh, we have to continue calling the task and and their response. Uh, we have to use the blue and try catch meter to get the response with particular model.

Yes. To manage the dependency among the various components within iOS projects, Firstly, I am, um, checking, like, uh, how many dependency we need, like, weeks, uh, third party libraries we need. After that, I will create the code file using the code unique command. And then after I will open the code file using the code open, uh, commands, and then I will uh, write down all the dependencies. And then after after closing the port file, I will install the port, um, using port install. And then after, we have to open the x c workspace file. And after that, uh, in the view controller file, we have to initialize with import and port them. So the library or the dependency will be, uh, loaded in that in that particular controller file. And then, yes, we can, uh, use it in our new controller file. Thank you.

Yes. Uh, I will implement the custom animation between 2 new controllers using the segment methods as well as, uh, if we can use u I u dot any meta animation method. And, uh, if we are using the constraints in there, then, uh, first of all, we have to change the concern when you like, uh, if I'm, uh, in general, I mean, my concern uh, idea outlets, then firstly, I have to change the value of that concern concern. And then after, I will just have to call the view, like, deep layout or view some layout matters, and it will automatically, uh, animate the v, uh, 2 views. Also, uh, in the views, view controller, uh, if I we have to change the view controller by, uh, using some animation, then we can also, uh, use, uh, uh, the navigation controller animation method, and we can beat that. Thank you.

Yes. For the efficiency storing and return user preferences in the iOS application, we can, uh, store the data in singleton classes and in the core data and user defaults. Uh, so singleton is used for the one time value. Whenever user applications reopen, we can, uh, find the value of data from the API and we can show it in the singleton class. Whenever the we, uh, clear the application or we close the application, the singleton data will be destroyed. After that, in the core data, we have to create the tables and we have to store the data with sessions. Like, if a user is, uh, doing the logging and then after, uh, user data will be showing the core data. And when our user is coming again next time and internally is not available, then we can retrieve the data from the database. And in the user default, we can use the same, uh, but it will be storing the user default methods. And in user default methods, we can store the data, uh, in different different models. And, yes, we can return the data, uh, from user default dot standard dot get will use. Thank you.

Yes. To handle the error in the suite, we can use to try catch method as well as optional binding and optional, uh, changing methods. Uh, whenever we are, uh, handling the errors, any errors in, uh, with using from the APIs, we can use blue and try catch method if, uh, we are passing any data in here. So then we can use blue and try to measure. And if we are handling the error from any model, then we can use optional training and optional binding. Yes.

Yes. In this code, when we are, uh, loading in the data and, uh, the run time exception will be list an ID, like, uh, if we have only items in the screen and we don't have the ID, that's why, uh, it will, uh, execute the runtime here. Thank you.

Yes. In this, it will missing the note task, uh, method at the end of URL session, like, whenever in the in this current code, URL session dot shared dot data task with URL. In at the end of call, we have to write those task method to, um, call them API or, uh, to call the network method. Yes. That's it.

Yes. We have used the, uh, MVVM, MVC, and wiper methods. Uh, that design patterns we have used the, uh, beside MVC. In the MVVM, we we will have the model view view controller. So we have 1 model view file, we have view 1 one con view controller file, and we have one data model file. That, uh, we are, uh, for the view model, we are storing the models and, uh, the API coding part in in the view, uh, model view, view controller. So in the view controller, we have the functions and logics, uh, everywhere. So, yes, uh, the new VM and apart from that, we have used the wiper. Uh, in the wiper, we have used the 1, v for wiper, I for index, and e for presentation, e for index, and ends, uh, r for, uh, the logical part. So, yes, there there are 5 types we have used in Wiper. Also, we can merge, uh, NVVM and Wiper both, like, uh, VIP and plus MVVM, uh, design patterns as well. Thank you.

Yes. To optimize the start up time of the iOS of regression, that will Yes. Uh, to start up the time of application, uh, we can avoid the initial run time API calling. Uh, in that case, we can, uh, call the API in the background process whenever the application is opening. Uh, it will directly show the flash flash screen and the home screen. In-depth, uh, we can, uh, parallelly, in the background process, we can call the API so it will, uh, deploy the startup panel by us.

Yes. So in the iOS set, uh, I'm debugging, like, from where I'm getting the trace. Uh, like, if we have getting trace from any force or anything or any, uh, do, uh, try catch block, I will use, uh, another method. It's like optional, uh, binding or optional wrapping, and, uh, we can find the we can do the debug and find the place, uh, what is the key missing. Like, sometimes in the index part, they'll create, sometimes the data is null. So null trace is also there so we can, uh, debug like that. Thank you.