When it comes to improving the performance of your Flutter app, sometimes it's not a single big bottleneck bogging things down, but the accumulation of smaller hits over time.
As Gordon Hayes points out here, the use of the "const" keyword is one of those smaller opportunities for performance gains. This is the case both in execution speed and memory use.
And just in case you're having trouble keeping the differences straight between "const," "static," and "final," Gordan also points out this older article from Bob Nystrom, which still applies today.
If you've been developing in Flutter for any length of time, I'm sure you've run into this one. :-)
Thanks to Filip Hráček for shining a spotlight on the root cause of these errors, and how to fix them.