Haha, guys 🙂 I think @gtnarg's suggestion to use a ViewModel when you need to store state is a good idea. It is technically very much the same as a Controller, but it's semantics suggests that it is a good place to put mutable state, and especially observable properties that are shared between multiple views. For the record: Scopes are not problematic at all, they provide clean solutions to many difficult problems. I might need to create a few screencasts to really showcase how powerful they are, and how they help clean up your code.