This is a practice that I suggest to every Flutter developer who wants to upgrade his existing application to the latest version of Flutter SDK.

(Optional) -> Create a new instance/user account to your existing Mac/windows system to not affect your current project settings and configuration. Because we can't take risk for existing project. I do the same on my MacBook, creating a new user login and configuring everything.

Now open a terminal and come to your project path. (c/path/to/your/project)

1. run 'flutter upgrade'

2. Update project dart version

      sdk: '>=3.1.0 <4.0.0'
   

3. Run 'flutter pub get'

4. Now let's update all the dependencies via the following command

    flutter pub outdated
   

   'flutter pub outdated' -> This command can help us to see all the possible versions.

5. Now once we have checked and reviewed run the below commands

6.  flutter pub upgrade --major-versions
    flutter clean
    flutter pub get
   

7. We can use 'dart fix' and 'dart migrate' while updating the dart version and error fix. Note 'dart analyse' also helps.

Hello developers... As you know I'm Kishansinh Parmar(You can call me Kishan = key+sun) a lead flutter developer at ketto.org. I built an application for Ketto's donors to donate more and help needy people.

Many developers and connection community friends are asking "Hey Kishan what are you doing and how are you maintaining the application as a lead flutter developer not by just writing the code."

"Hey Kishan what are you doing and how are you maintaining the application as a lead flutter developer not by just writing the code."

So today I'll try to explain my role and responsibility to understand well.

As a lead flutter developer or manager of applications, I'm responsible for overseeing the entire lifecycle of an application, from its development to its release and beyond. This includes managing the development team, coordinating with stakeholders, creating and sticking to a development timeline, and ensuring that the final product meets the needs of its users.

In addition, I'm responsible for managing the budget for the project, as well as allocating resources appropriately.

a lead developer should also be able to anticipate potential issues and risks that may arise during the development process and take steps to mitigate them. Additionally, they should be able to work closely with marketing and sales teams to ensure that the app is properly promoted and reaches its intended audience. Finally, a lead developer should continuously gather feedback from users and stakeholders to ensure that the app is meeting their needs and to identify areas for improvement.

This was a brief about the overall responsibility that I've to maintain and drive smoothly. Now let me try to explain in a developer way...

entire lifecycle of an application, from its development to its release and beyond

• Okay so let's assume we have 3-4 tasks in the current sprint all the tasks are different to vice versa. First, we groom together with product managers and the internal tech team to understand the requirements and outcomes for the end users. Then we add the estimation of the tasks and start development on the first day of the sprint.

• Now every day on morning standup we update the team with the following top 3 questions. These questions are relevant for all the tech team whether they are developers or QA's.

  1. What did you do yesterday?

  2. What are going to do today?

  3. Is there any blocker or not?

  4. Or is there any update to the team?

• Once we are done with the development, the developer will move the task to testing, so QA will test once if there are no BUGS based on requirements then the task will move to the next stage where the product manager needs to check the quality and mark READY FOR LIVE.

• Now once the sprint is about to close or tasks are READY FOR LIVE I've to merge and check the code quality based on internal code quality rules.

• We will publish first to BETA USERS only for the next 2-3 days. If all looks good we will roll it out for public users. (Here we are following the 20-50-100 rule where the first 20% of users will get the update and then so on for 50% and 100% of users)

allocating resources appropriately

• While we were grooming the tasks I had to measure task requirements and distribute them to other developers according to who can do the best for that.

• Once all the team developers understand about his task, they can start development

continuously gather feedback from users and stakeholders to ensure that the app is meeting their needs and to identify areas for improvement

• So once we roll it out to 100% public users we will see the task feature reports on how it is performing, if there any bugs are coming for that feature, What the user is saying about a new version and so on.

• So we try to collect the feedback and take improvement tasks in the sprint or is there any critical issue we take immediately to the current sprint?

What tools and processes do I follow for development to release and it's beyond?

• Hmm, interesting... I can distribute in the following categories.

• Sprint planning

  • ClickUp, Figma, Slack

• Development tools

  • VSCode, Android studio/XCode

• Grooming or brainstorming

  • tldraw.com, Notion for basic notes, and GSheet for roughly estimate task hours,

• Browser

  • arc,

print()

easy to start by logging in to flutter. Right 😀

Okay now, let's play with more sample log data.

1. "Hello world!"

2. "I\'m Kishansinh Parmar"

3. https://gist.github.com/imkishansinh/8653ff8054a5f64735e1712aa8329611

The result of the logs

As you can see that first 2 sample data print everything correctly but what happen with 3rd sample data? It discards some lines from the output, which we aren't expecting right?

If you output too much at once, then Android sometimes discards some log lines. To avoid this, use debugPrint(), from Flutter’s foundation library. This is a wrapper around print that throttles the output to a level that avoids being dropped by Android’s kernel.

The other option for application logging is to use the dart:developer log() function. This allows you to include a bit more granularity and information in the logging output.

Now let's print longer string outputs using the log() function. It works ✌🏻

So as we experienced the developer log() function makes sense for logging in to flutter. Nice

But, wait are you looking for something which is more beautiful for logging then try this package which helps you to log better visible logs.

Caution ⚠️: This package also reduces your log lines if a message is longer.

So my suggestion is to extend the logger class into your own class and gives your class more power with the developer:log function.

Tip: Extend Logger class to your own class