Yes it is likely that the native apps to be developed was the lowest level. Personal I’m dev. NET, I made a small application with a drop-down just to make mumuse, each element of the list posting a simple text. .
I tried to optimize by searching the web technology, but there is no way: as Mozart on my Nodo: ca saccade as in the Video and even worse on a long list ca makes holes between the elements during fast scrolling.
Indeed it makes sense that they use other tools that we did not ask either, but I do not think it is this that makes the biggest performance gain is especially a good knowledge of their Framework.
When you look a little ListBox precisely the net full article explaining why = virtualization items.
They must display. done at the same time and I doubt they use Blend, which is super convenient but adds a lot of useless things, I think the MS dev optimize their XAML (to a maximum of brushes and common resources, to avoid maximum size car, etc.)..
Other points: when seeking some performance we realize that there are things to be avoided like the Binding for everything.
JourFeries for the first versions were absolutely unbearable as I had done everything in binding, and nothing but the fact recalculate the dates of one year blocked a few milliseconds when the UI bin changes from year ca jerky.
Now I leave the binding for the design and I much code by hand to optimize or change the thread in the calculations.
But there are lots of article to load lists in another thread that the UI or using timers filling, etc.
There is a lot to say in this area and I think there is not really to my knowledge, a focus on such information, we have some articles in MSDN, after a lot of dev blogs from MS, but if you do not bookmark retouvent we do not (at least that’s what happens above that for the moment is a dilettante WP7) A + + Yanos..