Surendra kumar sharma

Yeah. I'm. Uh, I have 9 months experience in mobile application development for 11, I use a 9 year experience. So I, um, I have 3 experience with object to c language and 6 year experience with the Swift language. I developed a 50 plus application in my carrier. 30 plus 30 plus application was to to to deploy, and most of application available on Happy Store. And, uh, yeah, I recently worked on a poker card game, uh, using Swift UIKit feature. And, uh, I other related application was, uh, swapping business applications or training applications, even book event management application, book appointment applications, grocery application, And I also work with, uh, memory management, iOS permissions, location management, uh, in app assist feature, and, uh, iOS widgets, share extension, also working with, uh, iOS watch apps, and, uh, integration related to, uh, third party payment gateways, social networking integrations and applications, and and, uh, use, uh, Bitbucket and GitHub for, uh, code versioning and Jira, Asana, and, uh, ClickUp for both tracking tools, wide development, and I also use Figma and Adobe XD for, uh, design development part. And for I use, uh, normally, I'm using, uh, MVC and MBVM for, IS design patterns in development for it used for clean code in development and also working with, uh, unit testing with, uh, development. And that's all.

Excuse me, where you use design pattern to solve a problem. Nice. Uh, for iOS design patterns, uh, normally, I'm using, uh, MVC model view controller. And now in these days, we are using, uh, MVBM, model view model design patterns in, uh, ASW and development. And for your design patterns, how to problemize. If our is, uh, using multiple, uh, screens and using repeated view models in our code, then it will use to implement, uh, MVVM design pattern in our application. And, uh, MVC is containing, uh, uh, just, uh, all property and, uh, API calling feature in, uh, same controller. So using MVVM, uh, we can we need to create a separate view model part that it it will contain, uh, all property and data members in the view model and also, uh, same responsibility in, uh, view model for calling API. So so this view model, we can use for multiple screens in multiple view controllers, then it will be used for code reusable part in development. And, uh, should you do, uh, common view model? We can uh, write, uh, minimum code in development. And, uh, also, we can say it's, uh, 82 implement clean code feature in development. And suppose, uh, they have, uh, our login screen and sign up screen. So if we use MVC, then we need to create, uh, 2 2 separate controller, and, uh, both separate controller will be contain, uh, their own property and over API calling feature that is a part of MVC. And if we use MVVM, then then our single model view that can be used for, uh, both controller for login and sign up, and it's best example of, uh, uh, MBBM part that we are using reusable view model code in both screens.

To handle errors in network layer using saved. If the question related to, uh, API errors that we are getting in a response, then, uh, we need to create, um, for multiple, uh, errors handling in our, uh, network API class. And, uh, we can identify separate errors in with with their codes. And, uh, we can set a specific message related errors when we get from API response. And And if, uh, this error handling is related to our, uh, network layer, then, uh, we can use, uh, uh, there in actually, uh, iOS native is providing inbuilt, uh, network handling feature in a network layer class. So we can, uh, we need to inherit and, uh, use their, uh, our, uh, predefined error codes, and we can set their priority, which error can be used for their priority basis.

How would you manage state in a complex multithread iOS application? Uh, using, uh, combined framework that is providing a a synchronous a synchronously, uh, implementation of, uh, asynchronously flow. So we can set a property state in, uh, combine using publisher, and, uh, subscriber will provide their, uh, current state. And, and when our property is, uh, changing their data in a state, then, uh, complex then, uh, subscriber will provide, uh, their existing state, uh, that we added in publisher. So

Uh, using iOS animation, they have, uh, multiple technique to implement, uh, animation in iOS application. The the first, they have, uh, using, uh, iOS native UIA animation, and, uh, core animation is providing a multiple types of animation inbuilt, uh, native. And second, we can use, uh, third party script file using Lottie that is providing a script, uh, animation script file so we can implement in, uh, our application. And, uh, also, we can use, uh, any, uh, GIF image for a specific, uh, static animation that are repeating, uh, repeatedly. So and, uh, if any so using core animation part that is, uh, not affecting up our iOS application performance, so it easy to perform and easy to use in iOS native code. That is a best approach.

You're approach to optimize UI response in complex size. Uh, using, uh, size classes, we can optimize our UA responsive and complex application. Size classes is providing, uh, layout view of, uh, iOS app for every each and every devices with compatible feature. And, uh, this is providing the type of component, uh, regular, compact, and unspecified. These are size classes that we are using, uh, file development. And, uh, suppose our iPhone is in, uh, particular and landscape, then it will be used for regular regular. And, uh, if our iPhone is, uh, sorry. It's using for, uh, particular and, uh, horizontal. It's using a regular and compact. And our device in in, uh, landscape mode, then it will use for, uh, compact compact size classes. And if our device is related to plus devices, iPhone 7 plus, 8 plus related, then it's it's it's in a landscape mode, then it will be so compact regular size classes. And, uh, if size class is working with the iPad, it's normally regular, uh, regular. And, uh, also for, uh, landscape mode, also using for, uh, regular regular. Size class is basically converting uh, UI responsive UI for every devices for commonly. If if device is low low screen, then it's reducing their, uh, size plus a data and, uh, optimizing, uh, UI according to device responsive. And if device is large size, then it's, uh, scaling their UI according to device size in Landscam and portrait to both.

In this given snap code, uh, is function using dispatch queue property in a method, but its, uh, error will be so dispatch queue not in scope because this is, uh, declaring, uh, below of the method. So it should be declared before use in a method. Otherwise, we can use, uh, above of the method. Means, we need to initialize and declare before it uses that error will be solved.

What each? In the singleton pattern, And in the wrong in this information, how to fix. Using this code, uh, this is creating object, and we can say instance, like, app manager dot share manager. It's creating, uh, let manager instance. So using manager instant, we are calling a method, do something. So in this, uh, single drill pattern, uh, protocol, we can't create, uh, any reference, any object of the class because this is, uh, this singleton class is pointing a global global access in, uh, all of our project. So it should be used by app manager, share manager dot their method name and, uh, property name. So we can't create any other instance of or object of given class. That did.

How do you approach designing a scalable app app architecture for growing user base in iOS app? Designing scalable app. Architecture for growing user base in Azure. Using app architecture, uh, if app is saving offline data, then we can use, uh, our core services to save data in a core database like SQLite code data, and, uh, also, there have many preference in, uh, iOS. And if using, uh, our app, uh, using with, uh, Copua Touch architecture, then we can use our, uh, UI UIKit, game kit frameworks, event kit frameworks while development. And, uh, if I use app working with, uh, core OS feature like Bluetooth, then we can use core Bluetooth frameworks, and, also, we can use hardware related feature, like user authentication with device. They have local authentication framework. So, basically, architecture, uh, divided in multiple layers. 1st is, uh, cocoa touch. 2nd is a media media layer. That is a core services, and, lastly, it's a core OS. We can use based on their their, uh, u usability of the project to design a good scalable application. And if app our application is using, uh, like, media related feature, then we can also use media layer to processing on image, audio, video, and to get data from library and camera related feature. That each.

What method you are employed? I'm sure the Ios app user interface is still responsive. What method will you employ employ? Employ to ensure an Ios app user interface stay responsive during heavy computational task. User interface. Uh, you need to face, we can they have multiple way to implement Iosai. We we're doing different user interface to stay using to the way they're providing a, uh, coding part for the user interface in for application, and, uh, UIA kit is providing a storyboard and x a v can x a v can XAV controls for to preparing a design part and to implementing every computational task in design time. And I I will prefer to, uh, UI kit that is providing a multiple way to, uh, write, uh, heavy design in, uh, storyboard as overriding, uh, XAV files for separate UI customized controls by XAV controls.

How will majors with different disabilities. Accessibility of iOS application, there is, uh, provide a multiple ways. We can also use deep learning feature. So using, uh, customized URL, we can access our iOS application. And, uh, also, we can use various extension. We can access our application data in house out outside of iOS application. And, uh, there is also share extension feature so we can access our iOS application outside of iOS support. Share extension is basically used when we are selecting, uh, image from photo library. And when we say, uh, then, uh, uh, our app will be so in list to open image in our application support. That is a part of different way to open our iOS application for support. And, uh, first was deep linking. 2nd was, uh, iOS widgets. 3rd was cell extension. And, uh, also, we can, uh, set our, uh, local post notification local notification and, uh, remote post notification to access our application from outside the iOS app. And we can also get, uh, real time data without using our iOS application. And Yeah. No. And Uh, actually, deep linking, they have, uh, 2 techniques techniques to access our application. 1st is, uh, URL scheme, and, uh, second was, uh, universal link. So your list scheme also providing to open our app from outside, like opening open through Safari like that.