There are several similar questions in stackoverlow, but I did not find a clear explanation in any of the answers on how to implement the Action Bar template for more complex / multitasking applications.
As I understand it, there are two options for this:
1.) implement several actions and in each of them implement / enable the action bar -> The problem is that when you ever go to a new job, although it has the same kind of action bar, it has this transition and jumps through the screen, so this is obvious, this is a new “window”, a new separate screen and it kills this feeling of a single application navigation frame.
2.) Use a single FragmentActivity, with an action bar inside and with several fragments that inflate the content frame. -> This is a pretty good implementation of the action bar template, but the problem is that it contradicts Google’s recommendation that one fragment should be in one action in case of a phone. Or is it not so? From the “look”, I would say that the Gmail application runs basically this way.
3.) TabActivity - which is deprecated.
For the second solution (single action, multiple fragments), am I concerned that there will be any performance issue in the future? How does android handle memory in this case? Will he kill inactive fragments in free space, how does this happen with actions? Or will it kill the whole application, or will the user phone be overloaded?
, - , , Android :/
- ?
( 5-6 , )