Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not an issue But #43

Closed
akbarsha03 opened this issue Nov 6, 2016 · 1 comment
Closed

Not an issue But #43

akbarsha03 opened this issue Nov 6, 2016 · 1 comment
Assignees
Labels

Comments

@akbarsha03
Copy link

This looks very similar to the mosby library by hannes.. Could you please tell me what advantages i would've if i upgrade to moxy?

@senneco senneco self-assigned this Nov 7, 2016
@senneco
Copy link
Collaborator

senneco commented Nov 7, 2016

Hi! Well, before make Moxy, I did research. Mosby was most favourite library. But I not be fully agree with Mosby in some cases. Then we made Moxy with advantages:

  • You shouldn't be careful about activity/fragment recreate. You should not disable activity recreates or make your fragment retain. Only extends from MvpAcitivty, MvpFragment, e.t.c. or call MvpDelegate methods.
  • You can inject many presenters to one Activity, Fragment and other MvpView implementation.
  • ViewState is fully automatically. You should only apply @InjectViewState to MvpPresenter class. No enums, switch-case, flags, e.t.c.
  • Data of view commands shouldn't be serializable/parcelable. You can use plain object in your MvpView methods.
  • Boilerplate code is generated at compile time.

@senneco senneco closed this as completed Nov 8, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants