Android separate responsibilities examples.

Question

Hi All One thing about Android development i would like to see some examples on are, separating responsibilities in Android, right now i have Activities and i feel its quite unpleasant, how i put all my event handling, UI construction/updating and communication with my data persistence into a single Activity. This makes my Activities extremly "fat", also because of the way eventlisteners are implemented, i have alot of classes inside other classes, (im used to the idea of one file => one class). I tried separating some of the communication to external webservice into Services, but now quite sure this is the best way to do it.

What patterns apply well when developing Android, and you want to separate responsibilities. Ive been working alot with Silverlight MVVM pattern, im looking for something similar that apply well to the android environment.

Answer 1

It is good practise to separete the functionality. Make a class or a whole package which works with database. The activity should just call the appropriate methods.

In generally, activity should just handle/create ui and delegate the business logic or other actions to other classes.