On Nov 24, 2011, at 6:36 AM, Steven Pack wrote:
> Splash screen helps, but it really gives a bad impression for a user (and
> client!). Any tips for how to minimise startup time?
Do as little as possible within Activity.OnCreate(). :-)
The next release will help with startup time, trimming off o
Hi, yes I do have the splash screen setup like that, so there is at least
instant feedback the app is loading, but it then sits there just a bit too
long.
Good to hear it's set to improve in the next release... When might that be
pray tell?
On 26/11/11 12:18 PM, "Jonathan Pobst" wrote:
>Hell
Hello!
We've shaved about a second off of startup time for the next release
(measured on a Nexus One).
Also, you might want to try this method of splash screen, as the image
shows immediately when the user launches the app, before the monodroid
runtime is initialized.
http://docs.xamarin.com/
Thanks Chris. My issue with startup performance is from when I tap the
application to when I get my first chance to run code. Once I get my first
OnCreate() call on my SplashActivity, I do utilize background threads and
and IoC container, but it's loading the runtime that's the problem.
I know the
If you have a good amount of startup code which construsts various objects,
then I would recommend the use of an IoC container to introduce lazy loading of
those objects. I am using Funq, an open source library. It is highly optimized
and fairly easy to understand, as it doesn't use reflection t
It's a problem.
Splash screen helps, but it really gives a bad impression for a user (and
client!). Any tips for how to minimise startup time?
___
Monodroid mailing list
Monodroid@lists.ximian.com
UNSUBSCRIBE INFORMATION:
http://lists.ximian.com/mailm
