Silverlight TV 69: UX and Perceived Performance of WP7 Apps

Lately, you talk to much on SL-tv. I would like to see stuff like in the older episodes.

Talk is for radio.

Why is the audio so quiet? And I agree with the previous post - talk, talk talk. Channel9 used to have such concise, programmer-oriented content, now it seems to be marketing material.

Here is the blog describing the same

WP7Dev Tip 1– Optimizing the app by reusing already created visuals

 http://jobijoy.blogspot.com/2011/03/wp7dev-tip-1-optimizing-app-by-reusing.html

First, I really liked the work in that page and the idea of the content stream.

My question to Microsoft is why isn't the panel caching just a part of the framework? The phone knows what panel is current and what's on the backstack. At the very least (and maybe all you can realistically do) the framework should say, "Oh, there's a bitmap on the backstack -- lets compress it." And maybe you don't do it when its one level back in the backstack, but rather wait until its n-levels back.

Very good point @Kang, and that was my first thought before cooking my own solution to this problem. It could have been more effective if this kind of 'platform specific' issues gets solved in the SDK itself.  But again since it is mobile app, we dont deal with huge number of pages and navigation( IMDb is kind of expection it had 45 different pages and 100s of level deep it can get navigated from the home)

@Kang - I agree, my first thought was that this is a shortcoming of the phone's backstacking design - devs shouldn't really be performing clever acrobatics to avoid this.

Definately one for MS - the stack should be JIT virtualised. Still, this SLTV episode was really valuable for this point alone.

As for chat (Wiep) - I guess the show format has to strike the right balance between cold presentation and affable TV show.