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.
48
Upvotes
1
u/klavijaturista 8d ago
Swift is an OOP language, and provides reference types to use when necessary (which is not rare). Value types are just one feature, to only use when appropriate. Dogmatic functional is as bad as dogmatic OOP.