On 24/12/13 08:54, Zhu, Yongsheng wrote:
Letting web apps to do this themselves of course is a good idea. But trust me,
we don't live in an ideal world. You can educate developers how to write their
own similar splash screen but at the same time many users still need this. You
can see lots of requirements from construct 2 users to ask this usage scenario.
So basically we should provide a common splash screen mechanism for basic
usage. Besides, it also provides similar user experience as Android system
which is important to end users.
I agree to provide a combine solution like Kenneth said.
OK, thanks for addressing my concerns - it seems like you all have it
covered :)
Season's greetings!
Max.
Yongsheng
-----Original Message-----
From: Crosswalk-dev [mailto:crosswalk-dev-boun...@lists.crosswalk-project.org]
On Behalf Of Max Waterman
Sent: Monday, December 23, 2013 8:22 PM
To: <crosswalk-dev@lists.crosswalk-project.org>
Subject: Re: [Crosswalk-dev] Intent to implement - SplashScreen API for xwalk
based application.
On 23/12/13 19:34, Kenneth Rohde Christiansen wrote:
I think that is why there should be some max time before initial
layout finished, like say 300ms. If the app didn't finish initial
layout at that time the window will show anyway. That way you should
have time to show a simplified UI of your app, or a splashscreen (done
with JS + some background picture etc), and badly behaved apps will
still show up quickly, though their use experience won't be that good.
Also when creating a splashscreen you most often want it to fade
nicely into your read UI. That is what happens on iOS and is possible
to do with creating the splashscreen manually using JS and HTML/CSS
Agreed :) I look forward to implementing this.
I did an optimisation such as you describe for the 01.org scientific calculator
-
rendered the basic calculator UI with all the buttons greyed out, then went
about
doing the heavy lifting by loading the extra js, css, html and what-not, and
only
then enabling the app. IMO, it worked much better than a splash screen - it's
true
that this was an easier optimisation for this app than might be for others, but
I
think similar principles apply.
Max.
On Mon, Dec 23, 2013 at 12:11 PM, Max Waterman <max.water...@intel.com>
wrote:
On 23/12/13 17:50, Kenneth Rohde Christiansen wrote:
A combination of those two methods might be a better solution, or
could at least be researched.
IMO, that sounds like a much better solution.
Splashscreens always seemed like a bit of a cludge to me - just
covering up slowness that should be made faster or removed completely.
I do wonder how it would look to a user though - if the app is
particularly slow to start, then it will look as if the user hasn't
tapped the app icon properly and result in him/her tapping multiple times?
Worth looking into, though, for sure.
I hope someone is looking into how to minimise the time from the
first tap on the app's icon to the app actually starting - imo, that's the real
issue.
Max.
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
_______________________________________________
Crosswalk-dev mailing list
Crosswalk-dev@lists.crosswalk-project.org
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
