title: Android application architecture - MVVM or MVC?
body: <p>I got an android project I'm beginning to work on, and I want its structure to be as robust as possible.</p>
  
  <p>I'm coming from a WPF MVVM background and I've been reading a little about android applications architecture, but I just couldn't find a straight clear answer about which architecture I should use.</p>
  
  <p>Some people suggested using MVVM - <a href="http://vladnevzorov.com/2011/04/30/android-application-architecture-part-ii-architectural-styles-and-patterns/" rel="noreferrer">http://vladnevzorov.com/2011/04/30/android-application-architecture-part-ii-architectural-styles-and-patterns/</a></p>
  
  <p>and others suggested using MVC, but didn't specify how exactly it should be implemented.</p>
  
  <p>As I said I'm coming from a WPF-MVVM background, and therefore I know it heavily relies on bindings which as far as I understand, are not supported by default in Android.</p>
  
  <p>It seems like there is a 3rd party solution - <a href="http://code.google.com/p/android-binding/" rel="noreferrer">http://code.google.com/p/android-binding/</a>
  But I don't know if I'd like to rely on that. What if its development would stop and it will not be supported by future APIs and etc..</p>
  
  <p>Basically what I'm looking for is a thorough tutorial that will teach me the best practices for building the application's structure. Folders and classes structure and etc. I just couldn't find any thorough tutorial, and I would have expected that Google would supply such a tutorial for its developers. I just don't think that this kind of documentation handles the technical aspect good enough - <a href="http://developer.android.com/guide/topics/fundamentals.html" rel="noreferrer">http://developer.android.com/guide/topics/fundamentals.html</a></p>
  
  <p>I hope I've been clear enough and that I'm not asking for too much, I just want to be sure about my application's structure, before my code will turn into a spaghetti monster.</p>
  
  <p>Thanks! </p>