906952 - [meta] Investigate using ViewStubs to improve startup speed

Status: RESOLVED INCOMPLETE

(Firefox for Android Graveyard :: General, defect)

Description

[Shilpan Bhagat]

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.

Comment 1

[Lucas Rocha (:lucasr)]

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

Comment 2

[BMO Automation]

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](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.