Bug 320034

Summary: Slowness of the Plasma Active topbar UI after startup on Nexus 7
Product: [Unmaintained] Active Reporter: Shmerl <shtetldik>
Component: Top BarAssignee: active
Status: RESOLVED UNMAINTAINED    
Severity: normal CC: notmart, thomas.pfeiffer, tuomas
Priority: NOR    
Version: unspecified   
Target Milestone: unscheduled   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Shmerl 2013-05-20 02:20:25 UTC 
On current devel branch of Mer/Plasma Active running on Nexus 7, there is an apparent slowness of UI interaction with the top bar which is most apparent right after startup (until you touch the toolbar for the first time).

If you try to pull down the top bar it can take several seconds for it to start moving (in contrast, activity switching UI starts right away). After the first time, it becomes more reponsive, but there is still some perceivable lack of fluidity there in comparison to other UI elements which is somewhat irritating.

Reproducible: Always

Steps to Reproduce:
1. Start up the Nexus 7 tablet with Mer/Plasma Active (devel branch).
2. Try to pull down the top bar.
3. After that drag the top bar back and force.
Actual Results:  
Step 2 produced significant delay.
Step 3 has some perceivable annoying lack of fluidity.

Expected Results:  
UI should be very fluid and non irritating.
Comment 1 Shmerl 2013-05-20 02:21:49 UTC 
A side note - please add Mer to the list of platforms, for some reason it's missing from there, so I set it to "other".
Comment 2 Thomas Pfeiffer 2013-05-20 08:41:55 UTC 
The reason for this is that all the elements in the Peak & Launch area (the ones that are shown when you poll the Top Bar down) are only loaded the first time you pull it down, in order to decrease startup time.

Each time I present PA to someone right after booting, though, I get the feeling that maybe this turned out to not have been such a good idea after all: This is often one of the first things people to, and since it feels really really slow, the first impression people get from using PA is "Oh, it's slow!".

So I'm starting to think that maybe these elements should be loaded at startup after all, because it's probably less noticeable if the startup takes a few seconds longer than if an interaction feels horribly slow.
Comment 3 Aaron J. Seigo 2013-05-20 09:17:03 UTC 
I agree with Thomas; a fluid experience is more important than start up time.

Some analysis of why these components take so long to load would also be nice, but loading on start would be a good improvement imho.