Windows Phone 7 Unleashed Session 1
Download as PPTX, PDF2 likes709 views
The document outlines a session on Windows Phone 7, highlighting its application architecture, lifecycle, and hardware foundations, including design philosophies and user experiences. It also discusses key frameworks including MVVM, and the Windows Phone Marketplace process for app publication and validation. Moreover, it emphasizes the importance of integrating experiences and connectivity, ensuring relevant and connected user interactions throughout the application lifecycle.
Windows Phone 7 Unleashed Session 1
- 1. Bruce D. KyleISV Architect EvangelistMicrosoftWindows Phone 7UnleashedSession I
- 2. Session 1 : Getting Started
- 3. Session 1 AgendaWP7 – Phone OverviewApplication ArchitectureApplication Life cycleHardware FoundationApplication BarPanorama and PivotRed ThreadsMVVMMarketplace
- 4. A different kind of phone,designed for a life in motionPhilosophyCustomerDesignExperiencePlatform
- 6. The Windows Phone Design System Codename “Metro”
- 7. Integrated ExperiencesPEOPLE OFFICE PICTURES MUSIC+VIDEO MARKETPLACE GAMES
- 8. Standardized Hardware FoundationCapacitive touch4 or more contact points800 WVGA / 480 HVGASensorsA-GPS, Accelerometer, Compass, Light, ProximityCamera5 mega pixels or more, flash required, camera button requiredMultimediaCommon detailed specs, Codec accelerationMemory256MB RAM or more, 8GB Flash or moreGPUDirectX 9 accelerationCPUARMv7 Cortex/Scorpion or better480 WVGA / 320 HVGAHardware buttons | Start, Search, Back
- 9. Session 1 : The ArchitectureBuilding the Foundation
- 10. Software ArchitectureApplicationsYour App UI and logicFrameworksSilverlightXNAHTML/JavaScriptCLRApp ModelUI ModelCloud IntegrationXbox LIVEBingLocationPush notificationsWindows Live IDApp managementLicensingChamber isolationSoftware updatesShell frame Session managerDirect3DCompositorKernelHardware BSPSecurityNetworkingStorageA-GPS Accelerometer Compass Light ProximityMedia Wi-Fi Radio GraphicsHardware Foundation
- 11. Windows Phone 7 Frameworks DetailsWindows Phone FrameworksCameraDevice IntegrationLaunchers & ChoosersWindows Phone ControlsPhoneApplicationPagePushNotificationWebBrowserControlSensorsPhoneApplicationFrameSilverlight Presentation and MediaXNA Frameworks for GamesControlsDrawingIsolatedStorageDrawingGamerServicesMediaGraphicsShapesMarkupMediaNavigationAudioContentInputApplication ObjectCommon Base Class LibraryIORuntimeResourcesGlobalizationTextNetReflectionLocationDiagnosticsCollectionsComponentModelConfigurationSecurityServiceModelLinqThreading
- 12. Cloud IntegrationWindows PhoneYour Web ServiceCustom Web ServiceWindows Phone ApplicationExisting Web ServicesNotification ServiceLocation ServiceMicrosoft ServicesFrameworksCloud integration client servicesBuilt-in user experiences and APIs integrated with key Microsoft services
- 13. Familiar API frameworks for interacting with existing Web 2.0 services
- 14. Rich support for incorporating custom web services into app-specific experiencesUI Model: Familiar Web ConceptsWeb applicationProvide media represented as HTTP resources linked by URL’sPhone applicationProvides UI as XAML pages connected into cross-app flows by URI’sSystem trayShell frameRequests pages, renders UI, and handles navigation across appsWeb browserRequests HTTP resources, renders them, and handles navigation across sitesApp barSessions and back stackGroups together sequences of pages corresponding to a user’s activity across appsHistory and tabsGroups together sequences of HTTP resources corresponding to a user’s activity across sites
- 15. Session 1 : Page TypesBuilding the Foundation
- 16. Splash ScreenNot really a page… Just a jpg
- 17. Single Page
- 18. Application BarAutomatically added to new pageBut commented outCan be done in XAML or code behindTwo PartsApplicationBarIconButton (Limit 4)ApplicationBarMenuItemYou can set the opacity (0.0 – 1.0)Automatically Rotates and Adjusts
- 19. Application BarBest PracticesUse instead of your own menu systemUse the default system theme colorUse Opacity of .0 , .05, 1If Opacity is < 1 Screen is Full : Otherwise Screen will be shorterDo not use an Icon button for BackDon’t use more than 5 Menu items ( between 14 and 20 characters)
- 20. Panorama
- 21. Panorama
- 22. Panorama
- 23. Panorama
- 24. Pivot
- 25. Pivot
- 28. Keyboard Input
- 29. Application Bar
- 30. Panorama
- 31. Pivot
- 32. Splash ScreenSession 1 : Red Threads
- 33. Red ThreadsOptimize for “life maximizers”Red ThreadsA thread or a theme that runs throughout the entire user experienceThree Red ThreadsPersonalRelevantConnected
- 34. Red ThreadsPersonalYour Day, your wayPresent information that is pertinent to userConsider this almost as if every WP7 application should be like a dashboard the filters information down to your role
- 35. Red ThreadsRelevantYour people, your locationShow information pertinent to the environment the user is currently inAn example would be a locator for sporting events around the user based on GPS
- 36. Red ThreadsConnectedYour stuff, your piece of mindApplication should be able to interact with networked information (Cloud, online services) BUT not be dependent on thisMake sure the user experience is high even in a disconnected state
- 37. Session 1 : MVVMModel View View Model
- 38. MVVMMVVM stands for ModelViewView-Model
- 39. What's MVVM?an architectural pattern created by John Gossman from WPF team
- 40. is a variation of MVC pattern
- 41. is similar to Martin Fowler’s PresentationModel pattern
- 42. WPF Data Binding & CommandingViewViewModelModel
- 43. Motivation and benefitsTestabiltiy ( ViewModelis easier to unit test than code-behind or event driven code)
- 44. Clearseparationbetween User Experience designer and developer
- 45. Increases the "Blendability" of your view
- 46. Model never needs to be changed to support changes to the view
- 47. ViewModel rarely needs to be changed to support changes to the view
- 48. No duplicated code to update viewsMVVMView knows ViewModel
- 50. But not vice versa.ViewViewModelModel
- 51. ModelTypical class that covers a databaseCould be a WCF Service and its client reference
- 52. ViewModelProvides data to and from the ViewResponds to both the View and the ModelInforms the View of changes in the dataReusable (at least much more than code behind a form)
- 53. ViewModelKnows nothing about the ViewDoes not “push” data into the view TextBox1.Text = object.Name()
- 54. ViewUses Binding to “subscribe” to the ViewModelInterprets business data and state of ViewModel to the humanNothing but Presentation - XAMLNo or minimal code-behind
- 55. Cons of MVVMlack of standardization so everyone has own favor
- 56. For simple UI, M-V-VM can be overkillViewViewModelModel
- 59. MVVM Light
- 60. Caliburn
- 61. Silverlight FXSession 1 : Marketplace
- 62. Application MarketplaceEnhanced DiscoveryEasy to find great applications, games
- 63. Fun to browse the marketplaceSimple, Reliable AcquisitionTry before you buy
- 64. Buying and downloading content is a breeze
- 65. Payment flexibility (MO billing and credit card)
- 66. Easy application updatesTest Criteria Pillarstechnical validationpolicy validationmarket validationhttp://go.microsoft.com/?linkid=9730558
- 67. Publishing ProcessUpload Application (XAP)Meta Data (Icons, descriptions, icons)Check for size (< 500 mb)Recommended size < 20 MB for OTACheck Application code (No Native API)Check if Type SafeNo Debug SymbolsCheck for Phone CapabilitiesCheck languagesApplication and Game Submission.xap.xap.xap.xap.xap.xap.xap.xap.dll.dll.dll.dll.dll.dll.dll.dllAppPackaging &ValidationAppsubmissionMarketplaceWindows Phone 7 Deployment ServiceApplyTest CriteriaAddMetadataSignAdd Metadata and repackage application.Sign XAP and appears on MarketplaceCheck the app works (does it crash, hang, etc..)Start splash in 1 secondAccept user input 19 secondsTest for malicious code
- 68. Device Unlock for Application DevelopmentapiUnlock retail devices for developmentManage registered devices through thedeveloper portal3 devices/year1 device/year students
- 69. © 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
- 70. Live Tiles
Editor's Notes
- #2: Windows Phone is a whole new kind of phone, targeted specifically at consumers, who work hard every day to balance their work lives and their personal lives. These were the key focus areas for our design and development effortsNew philosophy on what the device needs to doFocus on the end user, not on enterprises Improved “glanceable” design paradigm with “Metro”Standardized experience across all devices, maanufacturers and all carriersStrong developer platform for building rich, interactive applications on the phone – a key part of our “3-screens and a cloud” strategyWindows Mobile Phones were essentially PPCs that got phone capabilities added to them. This device has been redesigned from the ground-up to be easy to use, incorporate the things you do and care about, and give you the information you need quickly and easily.Depending on the size of the crowd, I also ask about the screen shot here and ask for their feedback.
- #3: The Smart Design starts with what we call the “Metro” Design Language – not a language like developers would think of – but a natural language for expressing designs. The inspiration for the WP7 UX was based on signage around Metro Rail stations – clean, clear, easy to read information that you can take in quickly. We also refer to this as “glanceable” information – information you can take in at just a glance.It’s not about the fancy chrome, gradient fills or shiny, inactive icons – it’s about the information you need right now to get back to your “life in motion”…
- #8: Hubs are viewports into phone functionality – the phone UX is not about hosting applications, it’s about hosting experiences<build>There are 6 hubs in WP7 – developers can integrate their software into them
- #9: Windows Phone 7 Series has a very detailed hardware specification to ensure a consistent user experience for consumers across network providers. This way, phone customers will be able to continue using their existing service provider but get the same UX as everyone else. The consistent hardware and software platform also ensures that Microsoft can, through a centralized Windows Update mechanism, manage updates and patching to the phone platform in a consistent way, across providers.Highlights of slide: Detailed hardware spec to ensure a consistent user experience for consumersSingle display at launch, smaller display in future (lower price point for easier adoption)All capacitive touch devices – no more stylus!3 buttons only – not 5, not 1 – but 3Memory is minimum configuration, more is allowed
- #12: Connecting applications with data via Cloud Services One of the “3 screens” in our strategyYours: services that you write for your application, specific to your application, or part of a larger application deploymentTheirs: services built by 3rd parties (Netflix, US Government, SAP, etc) over open protocols (e.g. SOAP, REST, ODATA) for you to use in your S+S application.Ours: services built by Microsoft used with your phone (e.g. Notification, Update, Location), and applications you write for your phone (e.g. Xbox Live)
- #14: Building Silverlight-based UX navigation is similar to Web-based navigation:Navigation is from Page to PagePages are described as relative URIs (i.e. “/DetailsPage.xaml”)QueryString can be used (i.e. “/DetailsPage.xaml?id=123”)Back button is integrated and “smart” compared to the browser’s back button
- #47: InstallationApp codePhone capabilitiesLanguageCertification:- ReliabilityPerformanceSecurity