Welcome to part 2 of my series on Flutter Architecture:
Streams are the main building block of RxVMS so we will take a closer look at them in this post because understanding Streams is an absolute requirement to understand RxVMS.
It turned out that including Rx in this post would make it too long so I split it two parts.
I read a lot of comments that say Streams and especially Rx is too hard to understand, so they don’t use it.
I like you to know is that I don’t count myself a Rx wizard. Mastering the full power…
This is the fist post of a series of posts that will explain my take on App architecture for Flutter. It will be highly opinionated so be warned 😇
Unfortunately this article is already a bit dated and RxVMS has evolved to RMVS. As I don’t have the time at the moment to update it, please watch my recent talk on it here: https://www.youtube.com/watch?v=S_kx7XCNxjI
Still you will find worthwhile information in this post too.
Most people when starting with Flutter will start looking for a way how to access their data from the views to separate them. What’s recommended in the Flutter docs is using an InheritedWidget which not only allows to access data from anywhere in the Widget tree but also should be able to automatically update widgets that reference it.
Any descendant of
InheritedWidget should be immutable which means you cannot change its data but have to create a new instance with new data. …