Parth Virani (Parth Virani)

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

For Flutter, 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 event that we need to track, then on the tab of that particular event or opening the particular screen, we're just passing those data to analytics event like by creating a global instance of analytics and using the track event function. So in this way, we can send the analytics to Google Firebase Analytics. The best way to do this is whenever we find any important action in the application, like when a user adds anything to the cart or makes a payment or navigates to product details or shares product details. Anything like this will ultimately help us to generate some revenue or help us to track the user flow. So we always try to collect all those events. So in this way, we can identify the user flow or user tracking flow. By tracking user flow, we can provide a better solution. So in this way, they can use our application and perform better, and we can make better decisions in marketing and all those things. Yes. Importantly, it is very important to always integrate analytics. So in this way, whenever we run an ad or anything like that, we can track the user flow and all those things.

For solid principle, what I'll do is, generally, whenever I see a new feature, what I can do is I first start with some research, like, if any existing examples were there, then I try to analyze them and see how that particular example or existing feature was working in the report, taking reference from them. After that, I see the UI UX flow. Once I see my UI UX flow, I try to plan it based on and also check the API. So once I have all those things ready, like UI, UX, and API, I start planning making some basic screens. If any screen has Add, edit, or update, delete functionality, then what I do is just try to figure out what the main scenarios are to update or add. So in this scenario, we can ensure that the application has better performance or is easier to use, with all those functionalities. So whenever I design new features, I try my best to analyze and plan those tasks before starting development on them.

How can feature flipping work? Whenever we are adding any new features, we just elaborate on what that particular feature is doing. Like, if we're adding a download functionality, we just say that this way, at this place, the download functionality was added. And if it's in progress, then we progressively roll out new features to the mobile app. So, yes, once it's developed, we go for testing. And once testing is done, if any bugs or issues were received, then we just try to

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

To handle versioning of mobile apps API, what we can do is whenever we design or develop any new API, or a new version of the API, we just need to roll out the major new version, like v1, v2, and likewise. So what we have to do is we just need to keep running our old version, and move to mobile means try to upgrade the mobile application with the newer app, newer API version. In this way,

I think this is the better way to handle status calls. But my suggestion is to make getting and all those calls a common API class. So what happens is we just need to pass the API endpoint only, like slash user. So our base URL and all those things remain the same. Like we test out passing the URL base path. So in this way, we can handle and improve performance. And whatever error or anything we need to add, we can add at one place, which is a common API call. So once we add it there, we can have access to, or we can share that functionality on every call.

First of all, what happens is whenever we are doing any stream subscription, we always need to close them in the dispose method. And another thing is that once you are extending any class, like, one problem is this stateful visitor is not extending to a proper for, not extending properly to my custom visitor. So that will cause an error. And other things are, in each state and dispose are not overridden by default. So this will not execute. And to solve this problem, what we have to do is just extend my custom visitor, like, state and in brackets, we have to set my custom visitor and also override the unit state and dispose. And once we do override, just close the stream in the dispose method. So in this way, we can keep ourselves safe from leaking strings. So that's what's important.

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

Key component while integrating third-party UI is, I always try to first check if the core is updated or not. And even if it's updated, I always try to use the portion that I require, either by taking the source code or in those particular codes from the third-party UI component to my Flutter application. So in this scenario, I own my code, like, where whenever I have to update or anything, and need to change anything, I can easily change these things. So in this scenario, or in this case, I can.

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