3 ms·

Any chance you have any links so I can read up on this approach?

• happytoexplain 2mo ago
  I don't know iOS-specific links off-hand - I'm basically just referring to rudimentary state-driven UI. But implemented manually, without a framework, and therefore bug-prone for unfamiliar devs. For example (this is pseudo-code, I haven't written Swift in a long time): class ProfileViewController: UIViewController { struct State: Hashable { var username: String? var profileImageURL: String? } var state = State() { didSet { if state != oldValue { updateView() } } } // must be idempotent // must only read state and only mutate the view function updateView() { usernameLabel.text = state.username profileImageView.setImage(url: state.profileImageURL) } } Lots of stuff can complicate this: External sources of truth (CoreData, UserDefaults), reference types (no memberwise equality), self-mutating views (UITextField), continuously changing values that state is derived from (the current time). But the pattern is so simple it's easy to extend it to account for these things as needed, usually with another layer of `update...()`, e.g. `updateState()` from a CoreData observer.