Keshav kumar

Hi. My name is Keshav Kumar. I work as a software engineer in Flutter for last 4 years, and I have total of 5 years of work experience. I am currently working in LTM INT for last 1 and half years, and, uh, uh, my total experience is in Flutter is 4 years, and total work experience is 5 years in mobile application development. So in this period of time, I have worked on multiple large scale applications like, uh, the Baptist Health Project, which is developing for the web. And, also, I have worked on other technologies like, uh, mobile applications where we develop the Android and applications of different domains like ecommerce, cab booking application, flight and hotel's booking application, and multiples. So, uh, as we all know, I started, uh, so as we know that we started Flutter come in 2017. So right now, it's a pretty, uh, mature technology. So right now, uh, I have worked for around some of the large scale applications, like, which has uh, millions of users, uh, and active users, such like, uh, HSBC life insurance application, which is 1 of the Middle East, uh, application, which is used for the hotels and flight booking, which, uh, it is also live now in App Store and Play Store. And, also, the web app is also live, so you can go through them. And, uh, right now, I am working in 1 of the application of, uh, 1 of the clients of US with the for the health care domain, which is the Baptist Health uh, with LTM INT. So we are developing a new application that allow you patients to book the appointments and diagnosis tests so that all the tests, uh, medical tests that, uh, are that, uh, were required for, uh, the treatments. So we created a web application in Flutter with Get It and provider and, uh, other stream management platforms as well. So we use them to build a web app that allow users to book their appointments. And, uh, we, uh, and I have worked on multiple listing management platforms like, uh, Getex, Blocks, Cubates, uh, RXDAT, and much more. So I have a pretty good experience on the state management with Flutter.

So there are different ways to optimize, uh, a Flutter app with network issues when delivering with large payloads. So so we we try to add 1 of, uh, 1 of we can show the user that there is some request happening in the background. So we saw a continuous load as far as there is a delay in the network delay in the API response and the upload service. So this way, we manage and, um, some of the ways also that if it's not, uh, if that the thing which is working in the payload is not, uh, we need to show the user at the same time, then we try to show the user the next step of the flow in the of the of the user flow. And the API services happening will be happening in the background and user can continue through the application. And this way, uh, we can manage the application data and with large payloads we try to refract like suppose we are sending a video then there should be we try to compress the data that we are sending and wrap it in a single object of the request body and try to send it in the in the network request. And, uh, if the request was successful, then, uh, it will get updated, uh, in the it will get updated and the user can user was already in the flow and he can process with his interactions and can continue using the

So Flutter blocks. Flutter block, is 1 of my favorite topics where which is developed by, um, uh, Angelo Felix. So he's the contributor of the filter block package in pub.dev. So from the first application which I used, I used Flutter blocks. So for ink asynchronous data flow in Flutter, uh, we would, uh, the, uh, we use, uh, the Flutter, uh, emit methods to return, uh, the values that we get from the business logic. And we have, uh, block listeners, block consumers, block builders. So with block consumers, we can, uh, listen to the values and use it to represent the UI. Suppose we need to fetch any API call, so of today's, uh, suppose, uh, list of list of user data for their personal informations. So we will try to make an API call and, uh, with, uh, the, uh, and, uh, with the business logics, uh, it will give a response with the state that we have mentioned in the logic and which, uh, we can use to refer to that state in the consumer or listener to get that value. And that value, we can show with the consumer or builder in the UI that that user has that value. So if that stage is not shown, then we can simply show the user that uh, a continuous loader will be there. If we get that other the state that which we are using to represent, then we will show the UI with the data values. In this way, we manage the, uh, the asynchronous data flow in Flutter applications.

So error handling is 1 of the most common common uh, use uses of application development. So, uh, whenever we try to make any request, so there are multiple errors that were thrown during the, uh, API calls. So we had, uh, 1 of the, uh, uh, 1 of the packages like HTTP and DIO. So with the API with the network calls, if we get any use request, uh, if we get any error, then it will be shown, uh, in the response status code what error we have get and what is the response. So, uh, we, uh, try to add 1 we try to add, uh, the responses, uh, which we need to to to show to the user as per the status code which we get. Suppose, uh, we get, uh, some unauthorized access, then, uh, we will show the user that you don't have credential or access to the records so that we can manage from the HTTP and DIO packages, uh, with the the status code, what we are getting from the API response. And, uh, they are and, uh, as per the status code and the response which we are getting from the we can show different data or values uh, to the user that what is the exception and why the error is coming. So in this way, we manage the error handling of API calls in Flutter.

So, uh, so when we are developing the application, it's really required to make the Flutter code base maintainable and readable so that any developer who can start working on can understand the code and easily start working on it. So we try to make the code, uh, readable by adding some of the adding the comments that whether which code is related to what. And, uh, we try to follow the modular approaches and other design patterns to make to make the code maintainable that if any 1 part of the code get affected, uh, because of any errors or bugs, then it won't affect the other, other, uh, method or platforms. So in this way, we try other other modules. So in this way, we try to make, uh, uh, the code, uh, the code, uh, really stable and try to make it as more as readable by using, uh, proper name annotations for the classes and which represent the key features. In this way, we try to manage, uh, the Flutter code bases and, uh, and kt clean code base.

So, uh, the flutter, So Flutter tools, uh, like, uh, Flutter has own tools that, uh, which can use with Android as a studio. So Flutter performance is one of the Flutter tools that, uh, we use to understand what was the execution time of, uh, any code, uh, or any widgets, how much time it's taking. So and what is the memory usage, what is, uh, the UI how the UI is ending, how much space and time comp time it is taking to build the UI and perform logical perform logical operations. And, uh, we can also uh, we can also try to, uh, use one of calytics, the Firebase calytics so understand, uh, to understand, uh, if there any, uh, issue happen, uh, in the file, uh, in the app, to understand the logs, whether whether is the issue happening, uh, in the application when, uh, they are running. So this way, uh, the the Flutter app's performance were tested. So Flutter performance app, uh, Flutter, uh, Flutter tool is Flutter performance that is, uh, an integrated that comes with the Android, uh, IDE and Android Studio IDE, which we use to understand and see what are, uh, the performance, uh, issues and what the challenges that we face during the, uh, during, um, the, uh, app application run when the application is running and debugging.

So, uh, in this way, uh, so I try to ensure check whether the data which we are getting from, uh, or not to, uh, identity. Uh, I try to check whether the data which we are getting from, uh, the from the methods that we are calling, uh, is correctly, uh, marked or not. Then after we try to verify each each state information, uh, each time the state changes and try to check whether the return value is expected or not with the proper and, uh, settling the UI, uh, UIs frames as per the responses which we are throwing and try to check whether it is the value, uh, which we are getting is expected or not. If it expected, then, uh, we will, uh, need to then it will be good, and, uh, we'll try to progress in this way so that each and every logic that we are used to show any change in, uh, in an to show any logical changes, which will be shown here.

So, uh, this case is where when, uh, we don't have much resources to utilize and some of the packages that is easily available with, uh, the extensions. So then, uh, we can use them in our application. Suppose some of the third party packages that are highly reputable with the the public school and is the most common, uh, uh, third, uh, third party application. So this way, we can use it in our application, uh, in the pub's, um, in the pub's spec dot yml file as a dependencies. Dev dependencies, uh, and dependencies. So, uh, that will add, uh, then we can use use the, uh, codes that were there in the packages. Some of the packages that we generally used, uh, are like, uh, the HTML statement packages, block, q bit providers, and uh, other packages as well like intl for, uh, equitable for object comparisons and, uh, intl for link language and date time, uh, values, comparisons, and, uh, many more. We generally use in our application to maintain, uh, the application more smooth and consistent.

So, uh, Flutter, uh, so whenever we develop try to develop a Flutter application, it really takes too much time because at the first, it creates an IPK file, which is created every first time when we try to run an Flutter application. And, uh, and, uh, it takes too much time. So it is quite very much painful for a developer to to give that much time when you are creating an application. So we have some of, uh, we have to follow some of the design principles to make the application light. So we can use some of the common patterns like, uh, like, uh, dry state, uh, testing. Like, uh, we will try to remove the code and code code codes that are, uh, are not used anymore in the codebase, and we will make some of the common components so that, uh, are used that are duplicated for the implementation, um, in multiple files, and we will try to minimize the application side, uh, data storage that, uh, we we are using for to store the data of the users. So these are the ways some of the common ways which, uh, are used and which are used to make the application, uh, asset light and make it execution fast. And, uh, we will also try to manage the, uh, application. We will also try to make, uh, the performance testing of the application and and execution testing so that, uh, we will see what, uh, is the issue that is coming during the launch time of the application and try to understand that what can we do in in to make it more faster by removing some of, uh, the large, uh, some of the large module logics that are taking too much time where time and size time and memory size complexity, uh, is not better. So in this way, we will try to make the application much faster.

So, uh, I will try to use providers, uh, uh, with the Flutter block because they has some variables like change notifiers. So whenever we try to defers, uh, providers, then we can refer to, uh, that block and see what is there, um, with Aspect, uh, with Aspect because it's a a single subscription and, uh, multilisteners. So, uh, we can see an multilisteners approach so that whenever 1 value got changed, uh, in the block class, we can, uh, get that value in other in, uh, all the in all the listeners and try to see what data which we are getting from 1 block. So this way, uh, it's quite, uh, very helpful to manage, uh, uh, the states and make it more sim simple and reliable with flutter blocks with providers, uh, and, uh, quite a good approach to make for state management.

So, uh, like, flutter committee. Flutter committee, uh, I always try to be, uh, the 1 of the persons who be need to be engaged in this type of contributions where we try to try to add our, uh, try to add our views of, uh, the different tech which is going on, uh, in the Flutter. So I also have some of the repositories on GitHub that has that is that is to that is, uh, have some of the application developed to show the users, uh, to show the new developers that what are the responsibilities or who can they can how they can learn Flutter and understand the technology that we they, uh, that they are going to learn and understand. Like, it's 1 of the finest and niche technologies of today's time. So we have to, uh, we have to be, uh, we have to understand them to for a better career and also, uh, uh, an ease for an application development. So we tried, uh, our best to, learn and get learn and gather more of most of, uh, the best tech from the committee, and we also share, uh, our, our approaches to solve problems on different, uh, issues to to other developers and contributors.