My initial plan: Steps to add a collection: - Start an IAC with the collections app asynchronously - When adding a collection return only the collection names without saving to datastore or any other operations that delay the selection of the collection names. - Return the collection details in the activity response (with or without the icon not sure....) - Show the collection on the homescreen - Asynchronously save the collections to the datastore by talking back over IAC to the collections app. This approach is more complicated but gives us a lot more room for potential perceived performance improvements. Will measure the current times and work forward from there to ensure we have net gains.
Bug 1029609 - Will likely be fixed by this or the amount of blank screen time reduced at least.
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?]
QA Whiteboard: [VH-FL-blocking-][VH-FC-blocking?] → [VH-FL-blocking-][VH-FC-blocking+]
Vivien - do you have any suggestions before we go down an IAC route here? Something that would be nice would be some way for the activity to hide itself, but continue processing after calling postResult().
OS: Mac OS X → Gonk (Firefox OS)
Priority: -- → P1
Hardware: x86 → ARM
Whiteboard: [systemsfe] → [systemsfe][c=progress p= s= u=]
Whiteboard: [systemsfe][c=progress p= s= u=] → [systemsfe][c=progress p= s= u=2.0]
In my less then scientific test (since it requires me to actually choose an item) it takes 10-12 seconds before the home-screen _begins_ to display an icon.
Not going to be working on this (ended up working on something else today and my time for 2.0 is up) Even with 4s of that 10-12 being geolocation timeout we have a 4-6ss~ overhead.
Assignee: jlal → nobody
Since this was an investigation I'm going to close in favor of tracking this in bug 1029609 - I don't really feel like a spin-off is needed at this time. Thank you for looking into this James.
No longer blocks: 1029609
Status: ASSIGNED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 1029609
You need to log in before you can comment on or make changes to this bug.