Is it ok to have MVVM without model for temporary things? <p>Do you think it is alright from architectural stand-point to have ViewModel - View without model for temporary things?</p> <p>E.g.: I want users to input some paths so I can open some files later on. It doesn't make sense for me to store the paths anywhere just ViewModel and when the user clicks "Show all files" I then construct models of the files and ViewModels for View that represent them somehow. So really my only model is the model of the file.</p>