I can't seem to find a proper way to move on from ActivityGroup. I've seen Separate Back Stack for each tab in Android using Fragments
Take the following:
- An application with 4 tabs
- Each tab needs to have it's own back stack (similar to iOS behaviour, yes)
- The application may be tuned for tablets, so the back stack needs to hold Activities
Once you need to develop for tablets, the Activities will contain multiple fragments. Having a stack of Fragments won't work because Fragments can't be nested, so the stack has to contain Activities.
I can't seem to find a way around this other than to continue to use ActivityGroup.
Thanks!
EDIT 1: A concrete example.
Handheld:
TAB 1 -> Activity 1A (Fragment 1A)
-> Activity 1B (Fragment 1B)
-> Activity 1C (Fragment 1C)
Tablet:
TAB 1 -> Activity 1A (Fragment 1A and 1B)
-> Activity 1C (Fragment 1C)
@beyerss I don't think I can rely on FragmentTransactions consistently. I could add multiple fragments in a Transaction as you mentioned, but the Activity layout may not be consistent. Hence I'm still seeing the need for ActivityGroups.