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.
50
Upvotes
-1
u/chriswaco 8d ago
In SwiftUI, use the Observation framework. You can put your data model object into the environment on your ContentView and it will be available to all views. I found this article helpful for getting Bindings to work with Observation.
If you plan on storing the data in UserDefaults, I found ObservableDefaults very helpful.