Define Your Role | Lead Flutter Developer
I'm leading or guiding a flutter team(2-3 people) at ketto.org where I've to make apps in solid form which matches the industry app standards. I've more than 5 years of experience [2+yr remote] in mobile platforms
with service and product- based companies. I'm very
passionate to write code for thousands of users.
Introduction
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.
What did you do yesterday?
What are going to do today?
Is there any blocker or not?
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,
