Howdy everybody. I'm Eric, and I'm on the Flutter DevRel team at Google. I'm back with more questions about how Flutter devs design their apps. This post is a follow up of sorts to my previous post: "
"
Soon, I'm going to be working on documentation (and tooling?) that helps large teams with large code bases that need to scale. This documentation will include common design patterns that solve problems that most (or all) Flutter apps will face.
For example:
-
"How can I display a screen with cached data, kick off a network request to refresh that data, show the user that a call is in progress, and then update the screen?" (This question was asked to one of my team mates at Cloud Next last week.)
-
"What's are best practices when view-models (blocs, etc) need to communicate with each other?"
These questions are highly specific, but I'm also thinking about questions like "How granular should custom widgets be? How much composition is too much composition?"
My question for you: What kind of patterns do you wish there was documentation for, or did you bump up against in the past, despite it being something that all large apps need to consider? Or, are there any patterns that you feel like you solved and could be useful to others?
As always, answer however you'd like -- any conversation is valuable. And thanks for taking the time.