So Andrea Bizzotto brings up a good point here: When you're setting up your Flutter project, what is the best way to organize your folder structure within the project? Do you create a separate sub-folder for each major product feature, or do you organize the code around the kind of work the code is doing, whether that be UI presentation, data access, etc.?
I know that in my own projects I tend to lean toward the Feature-first option, but I hadn't considered too deeply a case Andrea brings up here, where sharing the code among a group of developers who don't need access to the entire code base might make me lean otherwise.
These are great thoughts, and I definitely think it's worth considering some of these tradeoffs, especially if you're just getting a new Flutter project off the ground.
Although Flutter officially supports building native Windows apps now, if you've previously done all your Flutter work in a Mac environment, you may not be familiar with the nuances you'll need to consider if you plan to also target the Windows platform, starting with the build process.
This great little tutorial by Tom Arra of Very Good Ventures covers what you need to know to get that Windows build going.