xingjiu created WEEX-27:

             Summary: Prerender
                 Key: WEEX-27
             Project: Weex
          Issue Type: New Feature
         Environment: Android, iOS, (not Html5)
            Reporter: xingjiu
         Attachments: TB12RlEQFXXXXccXFXXXXXXXXXX.jpg

In order to impove the page open speed, we have intro many ways, such as 
js-bundle prefetch.

Now we have a new idea of render the next page in background. When click the 
button to jump to the next page, just show it, no other js file execute cost 
We call it prerender.

First. Limition
Prerender will benifit user experience of waiting time of new page load.
It is like a tradition way, use extre space(memory) to reduce time cost.
We need to protected our app`s memory cost, so just one page can be 
prerendered. This limit maybe removed later.

Second. How we do?
One way is to store the callNative commander in memory.
We know weex use javascript engine to explain how the page will be render, then 
js will use callNative() to make native views created.
Once we just store the callNative commander, not to execute it. When the page 
is truely show, do the commander executed.
The attach image is the order of weex render steps currently.

Our goal is to make weex page show quickly.
We assure that using prerender, the page open in one second will reach 99.9+ 
precent. And the global festive main page will works prefect in prerender mode.

This message was sent by Atlassian JIRA

Reply via email to