Use Flavors

[lishaduck]

• Flutter (official docs)
• Very Good Core (docs on flavors)
• Flutter Ready to Go! (article by Julio Bitencourt)

We should also take advantage of flutter_launcher_icons and flutter_native_splash with their flavor support.

While I'm thinking about it, there was also a good series of articles on Medium that I stumbled upon which you might want to look at, @ParkerH27:

• Architect your Flutter project using BLOC pattern
• Architect your Flutter project using BLOC pattern (Part 2)
• Compile time Dependency Injection in Flutter
• Integration and Unit testing in Flutter They shouldn't be blocked, but even if the first two are, the second two shouldn't be. Also, for the third article, while it's a good read, inject.dart is deprecated, so if we wanted to architect that way, we'd need to use injectable instead.

[lishaduck]

dart_define should make this a bit easier.

[lishaduck]

dart_define did the job quite well. We might not even need separate entrypoints! Or even flavors for that matter. It could all just be env stuff. Also, the injection stuff should just work w/riverpod. And it does! I hadn't realized it could do more than just state.

[lishaduck]

Though the launcher icons are fun...

[lishaduck]

Closing, seeing as #103 covers what's left.