Skip to content
This repository has been archived by the owner on Aug 25, 2020. It is now read-only.

Migrate to MVVM architecture and Google's ViewModel #92

Open
fobo66 opened this issue Nov 12, 2019 · 1 comment
Open

Migrate to MVVM architecture and Google's ViewModel #92

fobo66 opened this issue Nov 12, 2019 · 1 comment

Comments

@fobo66
Copy link
Owner

fobo66 commented Nov 12, 2019

Moxy is kinda too complex for this project, and it turned out to be not so robust solution in terms of maintainability. So, need to find better architecture. Maybe we can try RxRedux, but Architecture Components seem to be the best choice, at least for now. Hope it will stay for the next couple of years.

Any library for the architecture seem risky now, because of what happened with Moxy.

@fobo66
Copy link
Owner Author

fobo66 commented Dec 25, 2019

It feels that it's too complicated and costly to switch architectures, and it will take a long time. So, first we need to refactor Moxy presenters and data layer in scope of existing architecture, and then we will see, is it worth it to migrate to another architecture

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant