Surajit Basak

Yeah. Hi. Uh, myself is, and I'm an adept professional in mobile software developer with more than 4 and a half years of experience. And in the, uh, working period, I have, uh, worked with native Android as well as I did with Flutter. And as a back end solution, I use Firebase. Uh, and, uh, I have developed many production here that, and a lot of them are also in the. And, uh, in in my, uh, working journey, I have learned a lot, and I can I'm, uh, eagerly, uh, excited to contribute my skills to your automation goals. So that's it, uh, on

So I firstly follow a clean architecture, uh, with the focus. Uh, and with with with the clean architecture, it's very easy to maintain and even scale, uh, any, um, Flutter code even if it it's a large code base. And, also, I, uh, like to test and, uh, unit test, uh, to to actually ensure that in the developing process, the existing code or existing UI is not breaking. So that's how I maintain a clean architecture and clean focus to actually help, uh, the focus to grow further and make sure it is also maintained by the successors of the program, uh, success of the technical development team.

Okay. I, uh, I'm not completely familiar with, data set.

Well, uh, I'll use any of the state management libraries like provider and index. State. And as I mentioned earlier that I, uh, handle the clean architecture in my corpus so that it is also scalable. I handle this type of complex, uh, user interaction with, uh, with handling the state. Also, uh, for API, uh, data fetching, I will use, uh, library like, uh, PO or HTTP. And, also, for local persistence in, I will, uh, find these, uh, that also, uh, handles the local persistent in. So with the help of these, I can handle these all of, uh, mentioned, uh, use cases in further.

Okay. Uh, for that, uh, Flutter also Flutter inbuilt a profile, uh, profile tool. Uh, like, uh, there is a 3 mode of Flutter, like dev app mode, release mode, and profile mode. I'll leave the profile mode for, uh, for actually debugging the performance of the app. I'll see, uh, if there is any jump on the animations or any performance lagging on any UI or performance, uh, or any UI interactions. I'll use the tech tools of this so so that I can, um, actually get to know about what what are the issues coming on performance. So Yeah. That approach I'll find.

Okay. Again, um, I'm not familiar with the block package. Uh, I'll, uh, yeah, I'll take that the I'll research about that block package of the missing.

Okay. For that, uh, I will, uh, apply the method for pagination. There is very large request, uh, or payload. Or I can use the list view dot builder, which actually reloads, uh, actually reloads the previous, um, pixels of, uh, the shown, uh, shown screen. Like, it recycles its view, so it does not create, uh, each and every time. The payloads, uh, get new audio. But, uh, I'll, uh, I'll go with the pagination 1. Like, I I only, uh, will fetch the initials, uh, initial data as long as the user can see those initial data. And if you the users pass through that, then I'll, uh, further access, uh, I'll further request, uh, the further data from the API. Also, um, I can use GraphQL for that. So GraphQL, I'll for, uh, on using graph, uh, GraphQL, I can request the, uh, amount of data that I need, not the whole, uh, payload, uh, which which which will be unnecessary for the user to download all the payload at once. If if he if he is not, uh, actually, uh, giving the all the all the data on this mobile app. So, yeah, these approaches, I will follow.

Okay. Uh, for that, I will use Firebase, uh, where I can integrate, uh, the login methods, like, for, uh, email, uh, with with with Google, with Apple, all this kind of, uh, login methods, I can implement with the using of with the use of router. So what I'll do, I'll ask router first, I'll add on authenticate with the, uh, with the service login service like Google, and I'll connect that to the auth to actually, uh, save the record to the Firebase. And, uh, I'll check. Uh, also, um, I'll, uh, I'll this helps also, uh, writing the security rules for the Firebase database, like, real time database and pass through database. If you can, uh, add checks, like, if the user is authenticated with Firebase, then only you can able to read or write through the database. Otherwise, uh, the Fireflies will not allow to, uh, any anonymous user, which are not logged in with Firebase, they will not able to read on. Right? So this security, uh, measures are there in in Firebase, which which can be easily done with the Flutter, uh, Firebase auth. So yeah.

Well, uh, it's it it was a quite good experience because, uh, actually, I before I was developing the app in native Android, but when I switched to Flutter, it actually fascinates the way it handles, uh, you know, the single, uh, single, uh, what, single page code with all the widgets code over there and also the functionality over there. So it actually fascinates me. And with this journey, I have learned a lot with the Flutter and also, uh, the amazing widget Flutter provides that actually really helpful. All the custom, uh, animations I can, uh, build with Flutter. I cannot build with, uh, the native Android. So, yeah, that experience is really good, and I really want to continue and, um, actually, uh, be a very professional product developer for this community. So yeah.

Okay. If it's absolutely necessary to actually, uh, dig in another state management solution, I'll definitely do so, but I would like to stick with the, uh, 1 state, uh, provider, 1 state management library as it is very easy to, uh, you know, scale with that, uh, single, uh, state management library. But if it's a genuine requirement that the Blatter block does not provide any state management that other state management solutions do, then I'll have to, uh, you know, add these external, uh, river port or provide a solutions into that. But But otherwise, I'll stick to 1, um, state management solution. It will be easier for, uh, maintain the app for the.