I\'m used to coding Java Swing UIs, and in those if you have some properties that change, and you want your UI to update, you would implement the observer/observable pattern
That's not generally the way that it's done. Take a look at the discussion here, in particular the link to the Apple documentation.
If you still want to do it the way you say you do, it's not particularly hard to implement something like bindings "by hand". You'd just create a "binding" object that knows how to subscribe to changes, and connects to a property of a view.
To actually answer how it's done - normally, you have a controller object that monitors the state of the model (acting something like an Observer), and updates the view object(s) as necessary.