Android: Performance

Coordinator
May 29, 2011 at 7:48 PM

As mentioned in another thread, the DB on the server is now a "full" DB with all the events from the 2010 festival. This can give us an idea about how the app will perform with that amount of data in its current form.

It's already now known that the "Current and upcoming events" activity will have problems under this new data, as it needs to show the user 28 scenes / places with the three next events. Sebastian and I have talked about this, and we might meet up during the week and take a crack on this, to see which possibilities we have. We'll keep you posted on this.

It's so far less certain, which other views, if any, that might have problems with the new data amount. I guess we'll have to see and prioritize any refactoring based on whatever the impact might be (I, personally, don't need to have refactoring for the sake of refactoring itself - if it works, we'd better use our time on features instead...)