Experiments with MVVM in Unity3d. Tried several tools, best of it - Unity-Weld. Data binding leads to less code to process ui setup & update, but more boilerplate to support with events. Anyway, it looks usable in prototype scenarios, when we don't care about performance.

• https://github.com/Real-Serious-Games/Unity-Weld
• Easy to use with INotifyPropertyChanged (+)

• https://github.com/jbruening/ugui-mvvm
• Errors on integration, but works (-)

• https://github.com/tinrab/DataBind
• Special way for binding, custom syntax for binding (-)

• When linked with INotifyPropertyChanged from ViewModel we can't modify models directly, only from ViewModel, and we need reference to it (-)

• Use thin ViewModel with backing to Model props/events
• No limitations to what exactly we modify, model modification events fired in all cases (++)
• More boilerplace code, but we can expose in VM only part of props, if required (-)

• With Unity-Weld we need valid model before Weld components Awake, can be solved with Script Execution Order (-)