Does anyone have recommendations for managing an asynchronou

Question

Does anyone have recommendations for managing an asynchronous UI state with Kotlin and RxJava Jwharton s talk here was great but I m not sure if there have been any developments since then <https www youtube com watch v=0IKHxjkgop4 amp feature=youtu be>

Casey Kulm · Answer

Even older and not Android related but a very similar talk I love watching is <https www youtube com watch v=1zj7M1LnJV4>

Seri · Answer

Thanks Mr < Casey Kulm> I ll give that a watch

alexsullivan114 · Answer

Do you have a specific UI problem in mind or are you wondering more about high level architectures that deal with asynchronous UI elegantly

Seri · Answer

Moreso the latter

Seri · Answer

I have the chance to choose an architecture moving forward and am trying to set up a good framework ahead of time

alexsullivan114 · Answer

I ve personally been a pretty big fan of something like `MVVM` assuming we re mostly concerned the with the UI portion of the architecture I ve found that having your view whatever form that takes subscribe to a stream of events allows that stream to be generated entirely asynchronously

alexsullivan114 · Answer

You can sprinkle in other buzzwords for the rest of your architecture like unidirectional data flow and all that jazz to spice things up

alexsullivan114 · Answer

but thats the biggest game changer I ve found so far Having the view in charge of subscribing to some source that emits some type of object that corresponds to UI state

Seri · Answer

Thanks for the insight < alexsullivan114> I was also looking into MVP and MVVM architectures and I think I just found a good set of examples

alexsullivan114 · Answer

Awesome good luck Let us know how it turns out

Seri · Answer

thumbsup

Casey Kulm · Answer

Unidirectional really does seem like a big game changer to me but unfortunately it hasn t gained as much popularity on native mobile development yet Redux is huge in the front end web world <https redux js org >

Casey Kulm · Answer

But yeah I like MVVM since it s pretty easy to do on Android at the moment Custom Views with a single setter that takes a View Model POJO

Casey Kulm · Answer

Little bit of stuff behind a Flux Facebook front end web library for Android <http armueller github io android 2015 03 29 flux and android html>

Casey Kulm · Answer

MVI clone architecture from CycleJS front end web apps for Android forking the Google Architecture examples <https github com oldergod android architecture>

Casey Kulm · Answer

^ my favorite

ghedeon · Answer

true one of the best mvi implementations on Android that I ve seen I like the concept but on a second thought it creates so much boilerplate code and so much dancing around even a miniscule things so I m not sure anymore

tschuchort · Answer

andre staltz is your guy if you want to read about unidirectional architectures He made a great overview although it s mostly web centric You should also take a look at the functional android reference app by paco estevez which takes a somewhat different approach In my opinion MVI doesn t scale well I m still trying out different things to find a good functional architecture but for a critical product I would stay with MVVM for now