I'm using the Google DrawerLayout
.
When an item gets clicked, the drawer is smoothly closed and an Activity
will be launched. Turning these activities into Fragment
s is not an option. Because of this, launching an activity and then closing the drawer is also not an option. Closing the drawer and launching the activity at the same time will make the closing animation stutter.
Given that I want to smoothly close it first, and then launch the activity, I have a problem with the latency between when a user clicks on the drawer item, and when they see the activity they wanted to go to.
This is what the click listener for each item looks like.
final View.OnClickListener mainItemClickListener = new View.OnClickListener() {
@Override
public void onClick(final View v) {
mViewToLaunch = v;
mDrawerLayout.closeDrawers();
}
};
My activity is also the DrawerListener, its onDrawerClosed
method looks like:
@Override
public synchronized void onDrawerClosed(final View view) {
if (mViewToLaunch != null) {
onDrawerItemSelection(mViewToLaunch);
mViewToLaunch = null;
}
}
onDrawerItemSelection
just launches one of the five activities.
I do nothing on onPause
of the DrawerActivity
.
I am instrumenting this and it takes on average from 500-650ms from the moment onClick is called, to the moment onDrawerClosed ends.
There is a noticeable lag, once the drawer closes, before the corresponding activity is launched.
I realize a couple of things are happening:
The closing animation takes place, which is a couple of milliseconds right there (let's say 300).
Then there's probably some latency between the drawer visually closing and its listener getting fired. I'm trying to figure out exactly how much of this is happening by looking at
DrawerLayout
source but haven't figured it out yet.Then there's the amount of time it takes for the launched activity to perform its startup lifecycle methods up to, and including,
onResume
. I have not instrumented this yet but I estimate about 200-300ms.
This seems like a problem where going down the wrong path would be quite costly so I want to make sure I fully understand it.
One solution is just to skip the closing animation but I was hoping to keep it around.
How can I decrease my transition time as much as possible?
Here is how I am doing it without having to define any kind of delay,
and the
LazyNavigationItemSelectedListener
can be an inner class ofMainActivity
.This answer is for guys who uses RxJava and RxBinding. Idea is to prevent the activity launch until drawer closes.
NavigationView
is used for displaying the menu.