Should not start fetching remote data before initial UI

[KeenWarrior]

This issue is currently in generic format and need to be further detailed

[shubhamvashisht]

I want to work in it.

[shubhamvashisht]

@garg-anuj can we break it into details?

[KeenWarrior]

@shubhamvashisht Approach I came up for this is. All aerogear pipe config and checking for auth should be moved after initial screen display. We can assume that auth state is same as last time app was visited.

[shubhamvashisht]

@garg-anuj as you mentioned the "initial screen display", is it about mainActivity before checking the auth status?

[KeenWarrior]

we can move auth status check and configure pipe to separate thread s it doesn't hamper UI. Additionally we may save auth state from last usage of app and assume state is same. Until we get to find out from other thread that there is some change.

[shubhamvashisht]

@garg-anuj great, can we break it into phases? i will start working on it.

[KeenWarrior]

@shubhamvashisht Move auth status check and configure pipe to separate thread as first mile stone

[m-murad]

@garg-anuj @shubhamvashisht @danielpassos
I think this will change the LoginActivity.java file.
If one is working on it, he should send the PR to @danielpassos branch.

(Just an opinion)