title: MvvmCross: Application wide view model?
body: <p>I am loving MvvmCross so far, but I am new to the MVVM technique.  MVVM seems to center around the View and ViewModel and navigating between them.  However, what about application-wide model items?  Maybe my application has a mode that it can be in that affects all views and viewmodel behavior.  This seems like an ApplicationModel or ApplicationViewModel.  Or maybe just use the App class itself to store application wide stuff?  What is the recommended practice for this concept?  If using the App class itself is a good idea, I assume there is an easy way to get a hold of the reference to the App instance from anywhere?  Haven't looked yet.</p>