Welcome to the Treehouse Community

Want to collaborate on code errors? Have bugs you need feedback on? Looking for an extra set of eyes on your latest project? Get support with fellow developers, designers, and programmers of all backgrounds and skill levels here with the Treehouse Community! While you're at it, check out some resources Treehouse students have shared here.

Looking to learn something new?

Treehouse offers a seven day free trial for new students. Get access to thousands of hours of content and join thousands of Treehouse students and alumni in the community today.

Start your free trial

Android

Posted by hadyhallak
hadyhallak
87 Points

Android View / Presenter model usage

Hello everyone,

I have used the MVP (model-view-presenter) structure in a recent android project and felt that the project took me more time to get done comparing to the normal android project structure. The process of creating a contract, and a presenter for each (Activity, Fragment, or a Custom view) was taking time and just seemed unnecessary, ignoring that it is just perfect when you go through android testing or junit.

So I am wondering, what is the best android architecture and why it is the best.

I feel that there is no size fits for all, it depends on the project type and requirements.