On 23/12/13 13:53, Li, Guangzhen wrote:
Thanks for your answers; glad that these issues are being considered :)
One quick follow-up question...
2) Isn't it true that, on Android, apps are started/stopped "on the
fly" and they need to store/restore their state so that they are
started again as if they hadn't been stopped? I wonder how a
splashscreen might interfere with this functionality - perhaps the
splashscreen can be set at runtime to 'fake' the most recent screen
image? ...but then, what about the case where the user switches
orientation while the app is stopped? Tricky...;
Yes, apps can running foreground or back to the background, and it
will be killed by the OS or restarted.
As my planning, The splash screen will be displayed only in two cases
1)The first time the app start up
2)When the app restarted (after killed by the OS)
When the app resumed (from background to foreground), splash screen
will not be displayed.
It is the correct behaviour to show the splashscreen when the OS has
stopped the app?
If you consider the app as a flow of screens, I would have only expected
a splash screen as the 'first' screen in that flow. I wouldn't expect to
see it just because the OS is starting the app, irrespective of if it
has been stopped by the user or the OS.
I suppose that expectation is debatable, depending on if you just want
to replace the 'white screen' with something more interesting, or if
you're really considering the flow of the app...ie, the user will see a
'white screen' when the OS restarts an app.
I am also wondering if the OS already shows a snapshot of the screen,
grabbed when it stopped the app (the same as it uses in the switcher, I
presume). Perhaps this is only for the 'resume'? My knowledge of Android
app lifecycles might be insufficient here, so please correct me if I'm
misunderstanding something.
Regards,
Max.
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
