Closed Bug 906952 Opened 9 years ago Closed 2 years ago

[meta] Investigate using ViewStubs to improve startup speed


(Firefox for Android Graveyard :: General, defect)

Not set


(Not tracked)



(Reporter: shilpanbhagat, Unassigned)



(Keywords: meta)

We currently inflate a lot of views which are not initially visible. Profiling showed we spend about 400ms inflating things. We can speed up things by viewstubbing a few of them and/or inflating them at some later point in time.
Summary: [meta] Investigate using ViewStubs to speed startup. → [meta] Investigate using ViewStubs to improve startup speed
Just re-posting what I wrote to shilpan before:

Sounds like a good thing to investigate. My main concern here is to not make the first interaction with tabs panel (or any stubbed part of the UI) feel clunky because of the lazy-inflation. One thing to experiment with is to force the viewstub to inflate just after we inflate the main UI i.e. postpone the inflation of the parts of our UI that are not immediately visible on startup.

Potential candidates for postponed inflation:
- Tabs panel
- Home pager (when it's not shown on startup)
- Toast bits
- Find in page bits
- Form assist bits
Depends on: 907592
Depends on: 909550
Depends on: 968640
Depends on: 970247
Keywords: meta
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly]( an issue can be reported at the [Fenix GitHub project]( If you want to discuss your report please use [Mozilla's chat]( server and join the [#fenix]( channel.
Closed: 2 years ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.