Project structure refactoring

Current project structure is not module wise and hence not easily maintainable. For example if someone wants to make some changes in the events showing page then he will need to search for related files in all of the directories. If our project structure is module wise such that all the related files will be contained in a module. For example app/events is a module somewhat like below -

events
  | EventsActivity.java
  | EventsContract.java
  | EventsPresenter.java

EventsContract will contain the interfaces required View.java, Presenter.java.

data should be separate module. which will consist one interface and one class implementing it. (For now)

This would make code readability better. reference - https://github.com/googlesamples/android-architecture/tree/todo-mvp

@niranjan94 @iamareebjamal @Ronak-59 What are your views ?

[iamareebjamal]

First we should look at implementing the MVP pattern, then we need to discuss how fresh the data must be for the organizer and how it must be refreshed if we use SQlite

It’s another issue of its own

[iamareebjamal]

This is an opinionated format and structure of that app is very simple for that use case

Imagine when interfaces will contain many methods, the contract class will increase in size and there will be unnecessary coupling

And google is not generally known to follow even their conventions right. Look at the broken AsyncTask API they try to push down our throat and even new architecture components which force you to write an MVVM implementation.

We should have as less coupling as possible.