![]() DataTemplates with a bunch of StackPanels and Grids? Try to simplify to a Grid with the right col/rows instead for perf wins.That sexy "tilt" effect? Use Peter's behavior and/or check out the MSDN docs.Check your apps for extra, un-needed background colors on pages, controls, etc. ![]() What is fill rate? 1.00 means one screen of pixels being rendered every frame.So if you have something in a pano/pivot item with 0 margin & padding, your UX will be funky.The panorama/pivot items expect most their contents to have a 12px margin left/right for UX reasons.Please use text styles and never hardcode sizes or default fonts.Using a map control inside a Panorama or Pivot is not recommended for a number of UX and technical reasons.You can set the Foreground property on Pivot to set the title and header text color.Having a single DispatcherTimer in your app can affect your battery life regardless of interval.Unfortunately the "Analytics" type from desktop Silverlight is not on the phone today, so you can't measure CPU in a regular app.If your UI thread gets pegged, your compositor thread will suffer.Your compositor thread should rock out around 60fps all the time please.long applicationPeakMemoryUsage = (long)DeviceExtendedProperties.GetValue("ApplicationPeakMemoryUsage").long applicationCurrentMemoryUsage = (long)DeviceExtendedProperties.GetValue("ApplicationCurrentMemoryUsage").long deviceTotalMemory = (long)DeviceExtendedProperties.GetValue("DeviceTotalMemory").However on devices with > 256MB, its cool to use more *in those cases.Remember that for ingestion to the marketplace, your apps need to consume under 90MB of memory.If you're using Panorama, a Resource background will load immediately compared to Content.Content over Resources for images means fast startup time Your 6-core machine running the wp7 emulator is NOT indicative of device (single core!) performance. If your app rocks and starts really quick *on a device* consider not using a splash screen.If you're not using PerformanceProgressBar, I'll send JustinAngel after you ProgressBar for Windows Phone 7.A Panorama with a billion items will take forever to load due to layout. So consider delay loading controls and screens.But like death, you eventually have to pay it for everything. A lot of people try building 'wizard' screens with panorama & pivot control.A slideshow app in 5 minutes: Pivot with null Header and Title and item headers.Wrap in a try/catch or wait for loaded (sorry!) Setting SelectedIndex before the items are set on a Pivot causes an exception.Beware that UI elements larger than 2000x2000 pixels that are bitmap cached clip on Windows Phone 7.Pivot and Panorama can have UI element headers and titles, too, but you'll need to apply your own styling (fonts and sizes).Even if you have a 30k compressed JPEG image, at runtime that becomes an uncompressed surface that may take several MBs of memory.Memory expands quick when you have a lot of views and images! Be aware of how many pano and pivot items you do have.You won't get the parallax effect, but it is another option. You can also set a Background image to a Pivot.Panorama looks nice, but Pivot will offer faster start time. ![]() It reads like a true guide to developing great apps on Windows Phone… ![]() Here’s some of those nuggets – I wanted to capture them before he left because who knows how long they’ll stay in Twitter. He was headed out on vacation but decided to throw out some words of wisdom for Windows Phone developers working in Silverlight. Jeff Wilcox is a developer on the Silverlight team and has been working on the Silverlight for Windows Phone initiative as well as the toolkit released today. Apparently Jeff saved his largest one for an avalanche of knowledge on Twitter in the late afternoon. On the heels of the Windows Phone Developer Tools and Silverlight for Windows Phone Toolkit releases I saw a lot of exhaling going on in the hallways today.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |