Closed Bug 871021 Opened 11 years ago Closed 11 years ago

Compare FragmentPagerAdapter and FragmentStatePagerAdapter implementations for home PagerView

Categories

(Firefox for Android Graveyard :: General, defect, P1)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
All
Android
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: bnicholson, Assigned: lucasr)

References

Details

(Whiteboard: fixed-fig, abouthome-hackathon) 

FragmentPagerAdapter holds fragments in memory and can be more responsive; FragmentStatePagerAdapter can help to conserve resources if there's a lot of state to maintain. Once more fragments have been created, we should be able to make a better decision about which adapter to use. We could also potentially use different adapters for different device constraints if necessary.
Priority: -- → P1
Whiteboard: abouthome-hackathon
Assignee: nobody → lucasr.at.mozilla
I'm leaning towards keeping FragmentStatePagerAdapter for v1. I'd only use FragmentPagerAdapter if the benefits in terms of responsiveness were quite significant (which I don't think it is). We can revisit this in the future. Closing this for now.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
Whiteboard: abouthome-hackathon → fixed-fig, abouthome-hackathon
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.