Hi guys, our app is getting bigger and more complicated lately, and I definitely noticed a loss in responsiveness and overall snappy-ness. Besides onCreate handlers becoming slower (we use lots of custom view drawables now, because the Android stock styles don't work for us anymore), sometimes, when a class is used for the first time, the Android class loader lazy loads that class which significantly slows down activity load times.
I was therefore wondering if you know whether it's possible and common practice to load activities and classes which are anticipated to be loaded anyway during application start, e.g. by using Class.forName or even explicitly calling Activity.onCreate simply to already have it readily constructed as soon as the user actually wants to use it? A loading screen would be shown meanwhile. I have never seen an Android app doing this, but on the iPhone, almost any application goes through a loading process when starting up. Any thoughts on best practices and solutions here? Thanks for your input, Matthias --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
