This task is really what Nikhil would call low-hanging fruit. Flutter is unique on the fact that you can create new objects with or without the "new" keyword (ex. child: Text() vs new Text()). Similarly to this, certain objects and properties do not have to be defined as constant (ex. size: EdgeInsets vs const EdgeInsets). Using the keyword "const" for all properties that do not change is industry standard practice, as it is a slight optimization that tells Flutter that it does not have to check the property for a new value every time it refreshes. This, along with other slight optimizations with constructors and whatnot, can be implemented to achieve maximum speed. Try to make our code as efficient as possible with industry standard practices.
I would also like for developers who are more experienced with Flutter to stay away from this task so that newer developers can get used to the layout of Flutter and how it handles props and objects while they perform this task.