Android - Create Application level fragment

Issue

For my current project, I will be using this SlidingUpPanel library.

The sliding up panel will host a fragment that will contain application/global level information. This panel will be in every activity in my application. This will be very similar to the way Google Play music works.

My question is, what is the best way to persist the sliding up panel fragment throughout my application? I see myself going about this in two ways...

1. Storing the fragment inside the Application class and loading it at the start of every activity (somehow, not even sure if this is a possibility).
2. Storing the data that it will display in the Application class & loading a new instance of the fragment, passing in the persisted data.

Which one of these two ways would be the best? Is 1. even possible? Are there any coding landmines with these approaches?

Solution

Storing a fragment to persist throughout the application lifecycle would be pretty unorthodox, mainly because the fragment class should be able to follow it's normal lifecycle events (in this case, mainly onPause and onResume) instead of being stuck somewhere in the application class.

It is definitely common practice to store the data and load it each time you display the fragment. If you want to enable some sort of cacheing or singleton pattern to access the data, it should most likely be with another object that the fragment can access but is not a member within the fragment.

There is a good video from google about leaking views and it touches briefly on the pitfalls of doing some similar to what you're proposing in bullet #1.

Answered By - jyanks