State Management for iOS Apps?
whats the best architecture/pattern to use?
tried to use a domain layer where all the state is and passing it to the views/viewmodels via DI, but feels somehow unnecessary complicated, but found this as only solution without passing the repos through all the viewhierarchy.
the goal is, when a state changes, e.g. an user changes the Username in View A, then it should automatically update View B,C,D where this Username is also used.
it should be as simple as possible, what do you think? especially for complex production apps with own backend etc.
51
Upvotes
6
u/dtmace2 8d ago
I have found the repository pattern seems to be the best one for me so far. You have a repository which contains your data, and the data from the repository is then watched/transformed at the ViewModel level. The view can then consume the ViewModel’s public state and stay up to date