Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

Web and WebWorks Development

Reply
Highlighted
Developer
Posts: 164
Registered: ‎11-27-2012
My Device: Z10 LE,Dev Alpha C
My Carrier: China Mobile
Accepted Solution

Would there be any performance improvement for webworks?

Would there be any performance improvement for webworks in SDK 2.0?

It's tooo slow,

my app needs almost 2 seconds to boot up

1.5 seconds for the splashing screen that I can't disable

0.5 second for a white web-view and bbui init

it's just too slow.

 

and when the app runs,the animation of bbui sometimes has lag

you can see it's not smooth enough to call it a native app.

 

would there be any improvement ?

 

or I have to switch to Casades / native  for a better performance? 

BlackBerry Cascades / WebWorks developer, Vendor name: anpho
Developer
Posts: 1,229
Registered: ‎03-20-2011
My Device: Playbook, Z10 LE, Dev Alpha B, 2x Dev Alpha C
My Carrier: 3, Orange, Vodafone

Re: Would there be any performance improvement for webworks?

Its a beta so less than optimal is to be expected

 

Just not that slow

 

I presume you're doing something in startup - loading something / externally loaded JS libs / compulcated DOM (BBui will get hurt by that)

 

 




Click the like button if you find my posts useful!
Retired
Posts: 1,561
Registered: ‎04-12-2010
My Device: BlackBerry Z10
My Carrier: Bell

Re: Would there be any performance improvement for webworks?

The splashscreen is displayed inbetween the time the user launches the application, and window.load triggers. As peardox noted, if you are loading many scripts, external resources, etc. this will increase the time for the window to load.

The white screen after the splashscreen disappears and until you see your content, is the time it takes BBUI to initialize and load its first content. If you are doing a lot of initialization, the pages are complicated with a lot of tags/elements, etc. this will also impact the load time.

Some developers will place a "fake" splashscreen (i.e. the same splashscreen image) on their main document, so that once window.load triggers, the image is showing (as if it's still the splashscreen) and only goes away once BBUI loads its first page.

In your case, this would result in 2.0 seconds of splashscreen.

Ultimately, there is also some inherent overhead in the application, but Cordova shouldn't be adding a whole lot really. Prrimarily we're looking at resource and framework load times / initialization.

Erik Oros | @WaterlooErik | eoros@blackberry.com | Developer Issue Tracker

If a reply has answered your question, please click Accept as Solution to help other visitors in the future.
Retired
Posts: 203
Registered: ‎12-18-2012
My Device: Z10, Q10, Q5, Z30, Z3
My Carrier: Bell

Re: Would there be any performance improvement for webworks?

There are actually a few performance enhancements in the beta SDK. It's unlikely to be noticable unless you are loading a large number of plugins or are making frequent API calls.

 

To add to Erik's comments about splash screen. The Cordova SplashScreen API eliminates the need to have a "fake" splashscreen in place while UI frameworks are initializing.

 

webworks plugin add org.apache.cordova.splashscreen

 Then in config.xml:

 

<preference name="AutoHideSplashScreen" value="false" />

 Now you have full control over when the splash screen is hidden:

 

navigator.splashscreen.hide();

 

Bryan Higgins
BlackBerry WebWorks
@bryanhiggins