Closed brewin closed 5 years ago
Indeed! All these mvi / redux architectures sounds good on paper but in complex scenarios it becomes a different kind of beast.
I would like to see RecyclerView and Dialogs using this structure. I tried without success, but Epoxy/MvRx has been the best for me/the closest I could get to multiple states, clean, and testable architecture.
Working on this, more to come in the DroidCon SF
Nice looking forward to it!
I watched it, but I still think you could have gone deeper into it (like with a RecyclerView or a seek bar instead of play/pause)
I tried the architecture and i think it’s great. It has it’s difficulties, for example what is a component and what’s a mere detail of a screen.
I would like to see from you an example of a dialog, snackbar or recycler view.
How can we use this with other layers of our app architecture like Presenters/ViewModels or should we get rid of them?
Also if we are using UseCases to communicate with a Repository, should we add the UseCases to Activity/Fragments and make the calls there or maybe create a new object/layer that takes a bus and react according given events?
@julianomoraes are there any updates on this? I am very interested in your take on the "more complex" approach 👍
I've been using MvRx with some insights from Juliano's approach and couldn't recommend anything else!
Stay tuned for this year's Droidcon. :)
Which one? 😔
You read a lot. We like that. You’ve reached the end of your free member preview for this month. Upgrade for unlimited access.
Could you please disable the medium paywall for that article?
done
It isn't clear to me how this architecture would work with more complex "components". A more fleshed-out example, such as a simple to-do list, would be helpful.