Inside Windows Phone #33 | Windows Phone 7.5 Refresh & 60% more Opportunity!

Download this episode

Download Video


This week we spoke to Dev Plat Program Manager Mike Battista about how we extended the great Windows Phone experience to run on more affordable hardware, and what it means for software developers.

And what does it mean? Tremendous new opportunities!

Given these changes, we felt you would like more information about exactly what we did to accomplish this, and what YOU can do in order maximize the impact of your applications on these new devices.

Here are some more links to relevant additional materials on this release:

If you have any questions, let me know!




Available formats for this video:

Actual format may change based on video formats available and browser capability.

    The Discussion

    • User profile image

      The guidelines suggest not to use WebBrowser control inside apps, does that mean all news related apps in "news+weather" category will have really poor performance on new affordable devices? 

    • User profile image
      Mike Battista

      The WebBrowser control is still supported and the performance on lower-cost devices is on par with the performance today.

      The guidelines surrounding the WebBrowser control are more warnings about running out of memory than harming performance.

      IE can consume a lot of memory when rendering complex websites. This is true even today.

      The WebBrowser control essentially embeds IE in your app, so if you allow users to navigate to arbitrary complex websites in your app, the memory that IE uses will be attributed to your app. This could result in your app running out of memory if the sum of your app's memory usage plus IE's memory usage exceeds the recommended 90MB limit.

      If you'd like to use the WebBrowser control, just be mindful of the content that users are allowed to load. If the content isn't very complex, then performance/memory issues shouldn't be a concern.

      If users can load complex content in the control and your app footprint is already large, you may want to consider using the WebBrowserTask on 256MB devices to reduce the memory usage inside of your app.

    Comments closed

    Comments have been closed since this content was published more than 30 days ago, but if you'd like to send us feedback you can Contact Us.