Last modified: 2013-01-18 03:57:39 UTC
From OTRS: 10/21/2011 15:09 - Edwin Braacx wrote: > Dear Sir/Madam, > > In the introduction to your app you mention the desire to have it work fast. By downloading a featured article each time the app is started the process of direct searching is slowed down. How about making the featured article an option which can be shut off? >
It should probably just come up at whatever you last left it on, previously cached, unless you 'backed' through the stack until there was nothing left, leaving the app to close. Fetching current info also shouldn't prevent anything else from going on (such as starting a search), so really shouldn't be slowing stuff down much. Is this about the modal spinner that prevents you from starting a search? Or assuming that's removed, is this about the network traffic of loading the initial page?
I bet its the initial load. If we can resolve https://bugzilla.wikimedia.org/show_bug.cgi?id=31761 then this becomes less of an issue after the first load.
I don't think this is spinner-related as such anymore; the spinner shows and works during this time, as expected. Problem originally was that there was a modal spinner which prevented you from doing anything! This is no longer the case -- you can start search immediately, without waiting for the page to finish loading. My inclination would be to close this out as fixed.
Taking the liberty of closing as fixed.
This is still coming up. Unless we have static content that were showing...lets add this as a config option
We don't seem to plan this currently. PhoneGap-based app is being discontinued in favor of future native apps, on which we plan to have much more consistent caching.
