An end-to-end experience of Windows Phone 7 development (Part 2)
- 2. Rudi Groblerhttp://www.rudigrobler.net@rudigroblerAn end-to-end experience of Windows Phone 7 developmentTRACK: NEXT GENERATION
- 3. agendaTwo part sessionThe basicsBuild app from File -> New…Advanced tips and tricksLoads of contentCaveat: this is NOT a marketing session on how cool the phone is… This is how to build a application end-to-endFeel free to ask questions ANY time...Windows Phone 7 App Smackdown
- 4. applicationsOmoplataScrumy7PodiumProfessional Audio Recorder7MC GoferBrew Master
- 6. hardware foundationCapacitive touch4 or more contact pointsSensorsA-GPS, Accelerometer, Compass, Light, ProximityCamera5 mega pixels or moreMultimediaCommon detailed specs, Codec acceleration800Memory256MB RAM or more, 8GB Flash or moreGPUDirectX 9 accelerationCPUQualcomm MSM8x55 1Ghz (800Mhz) or higher480Hardware buttons | Back, Start, SearchQualcomm MSM7x30 & Gyroscope
- 7. common platform capabilities.NETSuperset of Silverlight 3.0InputTouchHardware buttonsMediaDigital media capture & playbackMedia library accessDataIsolated storageLINQObjectXMLWCFSOAP & REST servicesPhone AccessIntegrated access to phone UISensorsPickers for contacts and photosIntegrated with Cloud ServicesApp deployment & UpdatesNotificationsLocationXbox LIVE
- 8. Two flavours of applicationsSilverlightXNAModern XAML/event-driven application UI frameworkRapid creation of visual stunning applicationsMetro-themed UI controls500,000 developers spanning Windows and webHigh performance game frameworkRapid creation of multi-screen 2D & 3D gamesRich content pipelineMature, robust, widely adopted technology spanning Xbox 360, Windows and ZuneXNA/Silverlight Interop
- 9. silverlight for windows phoneSilverlight for Windows Phone is…Silverlight 3minus a few things that didn’t make senseplus a few Silverlight 4 things that didplus phone specific API & “under the hood” improvementsSilverlight 4 compatibility (1500+ new APIs)
- 11. navigationApplications are built like web sitesFunctionality is split into pagesForward navigation via linksBackward navigation via BackPrevious applications (pages) are in the back stackCan override back button behavior (but be careful)Transient pagesPayload can be send with navigation requestNO back to home buttons!!!Deep linking
- 12. Navigationdemo
- 13. familiar web conceptsPhone applicationProvides UI represented as XAML pages connected into cross-app flows by URI’sWeb applicationProvide media represented as HTTP resources linked by URL’sShell frameRequests pages, renders UI, and handles navigation across appsWeb browserRequests HTTP resources, renders them, and handles navigation across sitesHistory and tabsGroups together sequences of HTTP resources corresponding to a user’s activity across sitesSessions and back stackGroups together sequences of pages corresponding to a user’s activity across apps
- 14. launchers and choosersWindows Phone execution model isolates every application in its own sandboxApps cannot directly access information stores such as contactsCannot directly invoke other applications such as phone or messagingLaunchers and Choosers allow applications indirect access to the useful phone featuresLaunchers and Choosers APIs invoke distinct built-in applications that replace the currently running applications
- 15. launchers and choosersLauncherLaunches one of the built-in applications though which a use completes a taskNo data is returned to calling applicationExample: PhoneCallTaskChooserLaunches one of the built-in applications through which a user completes a task and which returns some data to calling applicationWhen caller completes, calling application is activated and supplied with the Chooser resultExample: PhotoChooserTask
- 18. choosers and the execution modelIMPORTANT! When you launch a Launcher or Chooser, your app is terminatedWhen task completes, your app may be reactivated and a new app instance created (SOMETIMES)The following choosers and tasks have relaxed thombstoning policyPhotoChooserTaskCameraCaptureTaskMediaPlayerLaunchTaskEmailAddressChooserPhoneNumberChoose
- 19. panoramas
- 20. panoramas
- 21. pivots
- 22. panorama vs pivotPivotPanoramaFilter same data on different views (the “inbox” is a great example of this) Optimized for current screen size Filter of data doesn’t have to be same view (agenda/day) Related content is ok to pivot on as long as related content is truly related Focused “Virtualized”Horizontal broad canvas, not confined to current screen size A ‘top layer’ view into underlying experiences/tasks Use white space Performance -> Panorama loads all the pages on startupExploratory in nature
- 23. Adding and using the Pivotdemo
- 24. misuse of common controlsUse the WP7 common controls appropriately.Don’t use sliders, toggles or map controls under panoramas or pivots –as they both need the same gestures to work.
- 25. MVVM on the PhoneSingletonApp.xamlModelPhoneApplicationPageViewModelPhoneApplicationPagePhoneApplicationPagePhoneApplicationPageViewDataBindable propertiesBusiness logicPhoneApplicationFramePhoneApplicationPageControlsCode-behindWanna learn more? Check out Silverlight Kung-fu Starting 16:30 @ track 3
- 27. networking on the phoneSupport for networking featuresWCF/ASMXHttpWebRequestWebClientNo cross-domain policy file requiredNot supportedSocketsCustom WCF BindingsWCF RIA ServicesNTLM authentication
- 28. WCF/ASMX servicesCan “Add Reference” from Windows Phone projects to automatically generate proxy classesASMX should just workWCF requires that you use basicHttpBinding
- 29. ODataServer:WCF Data Services provides an extensible tool for publishing data using REST based interfacePublishes and consumes data using Odata web protocol Format is XML or JSONClient:Download Odata Client Library for Windows Phone http://odata.codeplex.com/FULL parity with Silverlight (Including LINQ and Add Service Reference support)
- 30. Getting datademo
- 31. HTTPWebRequestvsWebClientUse HttpWebRequest whenever possibleUse background thread and marshal back to UI thread (Using Dispatcher.BeginInvoke)WebClient is “easier” to use but happens on the UI thread no matter where it was spawned (Bug)6 Parallel requests limitWebClient bug fixed
- 32. marketplaceEnhanced DiscoveryEasy to find great applications & gamesFun to browse the marketplaceSimple & Reliable AcquisitionTry before you buyBuying and downloading content is a breezePayment flexibility (Monthly billing and credit card)Easy application updatesSouth Africa WILL BE supported…
- 33. marketplaceIt costs nothing to download the Windows Phone SDK and write code using the emulatorTo sell applications you need to register as a developerThis costs $99 a year and allows you to publish any number of fee applications and up to 99 free applicationsEach additional application costs $20Students can sign up for freeRevenue sharing (30/70)
- 34. yalla appsAre you looking for a viable alternative to publish your WP7 Apps to the Windows Phone Marketplace? Yalla Apps provides the solution by publishing your apps to the Marketplace on your behalf. Publish your apps to the Windows Phone marketplaceand unlock your device for testingShare and download code in the Module MarketSmooth certification processJoin the developer community
- 35. yalla appsUpdatedDevice UnlockingYalla Apps offers a device unlock service which allows you to unlock your Windows Phone 7 to debug and test applications. The device unlock is accomplished using remote assistance access to your development machine and charged 0 Credits for the first device and 50 credits per additional device.
- 36. Yalla Appsdemo
- 38. Don’t forget the Xbox Kinectshow-down after sessions this evening!
- 39. DevDays 2011 SponsorsPLATINUM SPONSORwww.bbd.co.zaSILVER SPONSORwww.dvt.co.zaSILVER SPONSORwww.ctutraining.co.za
- 41. © 2008 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.