Parth Virani (Parth Virani)

Uh, myself, Parth Virani, and, uh, I am a senior Flutter developer working as a full stack Flutter developer at Private Limited company where I am managing my team and, uh, also training them. And, uh, apart from that, I'm also managing them to do some work on the project along with me. So what mainly, uh, my development are up to mark. And The picture behind me is of snow, which uh

For Flutter, uh, for Google Analytics, we are integrating them using the Google Analytics tool library itself where we can integrate them using Firebase. What we are doing is whenever there is any action or any, uh, event that we need to track, then On the tab of that particular event or opening the those particular screen, we're just passing those data to analytics event, uh, like, uh, by creating in global instance of analytics and, uh, using the track event, uh, function. So in this way, we can send the analytics to Google Firebase Analytics. Now The best way to do this is, uh, whenever we find any important action in the application, like, When user adding anything in the cart or making payment or, uh, navigate on to product product details or sharing the product details, Anything like this which will ultimately help us to, uh, generate some revenue, or we can, uh, which which will help us to track the user, uh, flow. So we all Always try to collect all those events. So in this way, we can identify the user flow or user, What we can say is user tracking flow. By tracking user flow, we can provide any means and, uh, provide them a better solution. So in this way, they can use or They can use our application and to perform better, uh, and we can make a better decision in marketing and all those things. So, Yes. Import uh, very important things is, uh, always integrate analytics. So in this way, whenever we run ad or anything like that, We can track the user flow and all those things.

Uh, for solid principle, what I'll do is, generally, whenever new feature Is whenever I see a new feature, what I can do is I first, I, Start with some research, like, uh, if any existing example was there, then I try to analyze them how That particular example or existing feature are working in the report, taking reference from them. After that, what I do is I see the our UI UX flow. And, uh, once I see my UI UX flow, I try to plan them based on and also checking the API. So once I have all those things ready, like UI, UX, And, uh, API, I start planning making some basic screen. Like, uh, if any any screen has Add, edit, or update, delete functionality. Then what I do is just, uh, trying to figure out what What are the main scenarios to update or, uh, update or, Uh, adding. So in this scenario, we, uh, in this case, we can ensure that the application has better performance or better, uh, easy to use and all those functionality. So whenever I design new features, I try my level best to, uh, analyze and plan the those tasks task before starting development on it.

How can feature flip? Uh, whenever we are adding any new features, we just try to Elaborate what that particular features are doing. Like, uh, if we adding any download functionality, And we just say that this way, uh, at this place, the download functionality was added. And, If it's in progress, then we just progressively roll out new features, mobile app. So, yes, once it's, uh, developed, we are going for testing. And once testing is done, Uh, if any bug or anything was received, then we just try to

To share the Flutter framework code with I was saying, what we can do is we can use the platform channel or method channel where we, uh, just calling the method channel function to the native or native code. Like, uh, if in Android, we can call the native method. So what happen is native functionality will handle all the required processing stuff. And once the result is ready, They will send back to to Flutter side. So in this way, we can use the method channel and platform channel to handle, uh, platform specific

To handling versioning of mobile apps API, what we can do is whenever we, uh, design or develop any new API, Right? Or a new version of the, uh, API, we just need to roll out the major new version, like, v 1, v 2, and likewise. So what we have to do is we just need to, Keep running our old version, and, uh, move to mobile means, uh, try to upgrade mobile application with newer app newer API version. So in this way, uh

I think this is the better way to handle, uh, uh, status call. But, uh, uh, my suggestion is To make get and all those calls is a common API class. So what happen is we just need to pass the, What I can say is API endpoint only, like, uh, slash user. So our base URL and all those things are remaining same. Like, uh, we test out to pass the URL base path. So in this way, we can handle and improve the performance. And, uh, Whatever error or anything we need to add, we can add at 1 place, which is a common API call. So once we add over that place, we can have access on, Or we can we can share those functionality on every

First of all, what happen is whenever we are doing any Uh, stream sub subscription, we always need to close them in dispose method. And Other thing is that once whenever you are extending any class, like, uh, one One problem is, uh, this stateful visit is not extending to a proper For, uh, not extending properly to my custom visit. So that will cause an error. And other thing are, uh, in each state and dispose are not override by default. So This will not execute. And to solve this problem, what we'll what we have to do is just extend the my custom With my custom visit, like, state and in bracket, uh, caret bracket, we have to, Uh, set my custom visit and also, uh, override the unit state and dispose. And, Once we do override override, uh, just close the stream in dispose method. So in this way, We can, uh, keep ourselves safe from, uh, leakaging, uh, string. So that's what, uh, important

Offline first mobile app using Flutter where data. Uh, what we can do is whenever we In offline first application, what we have to do is we have to integrate SQLite database. So What happen is whenever any new data was entered in offline application, that those data will first go to escalate database. And once user has active connection, then those data will be sent to server. And whatever New data is available on server side. We have to fetch from that server And save them into escalate database. So the data syncing is need to be crucial part and, uh, need to be done simultaneously. So if user has a active connection, then that will be good. But if it's not, then we need to use Proper escalate database. So in this scenario, we can sync with our server and vice versa.

Uh, key component while integrating third party UI is, uh, I always try to first Check that if core is updated or not. And even if it's updated, I always try to use the portion that I required, Either by taking those source code or in, uh, those particular code from third party UI component to, my Flutter application. So in this scenario, I owe I on my code, like, where whenever I have to update or anything, and need to change anything, I can easily change these those things. So in this scenario, uh, or in this case, I can

Uh, to To develop CICD pipeline, I always prefer beta versions. So over there, I can see the build process, like, uh, automatically need to increase the version. And after increasing those versions, uh, first of all, what in CICD, I have to do is first set up the system by setting up in the studio, and Xcode, and Flutter, all those things on CICD platform. And after that, Uh, once those system are set up, we need to fetch the GitHub project over there and, uh, increase the So it's called by 1, number 1. So in this scenario, we can, Uh, create the build and upload to the Google Cloud and AWS.