Preparing for WP8
•
1 like•1,026 views
Slides from presentation given at WPUG, DDD10 & DDDNorth about what's coming in WP8 and what developers can do now, before more information and the SDK are available.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to Preparing for WP8
Similar to Preparing for WP8 (20)
More from Matt Lacey
More from Matt Lacey (20)
Recently uploaded
Recently uploaded (20)
Preparing for WP8
- 1. PREPARING FOR WINDOWS PHONE 8 Matt Lacey @mrlacey
- 3. http://www.DevEvening.co.uk/ @DevEvening
- 4. me
- 5. you
- 6. There's a new version of Windows Phone coming… - But what does this mean for developers? - What's new? - What's changed? - How do you upgrade an existing WP 7.x app? - How do you support WP7.x & WP8 with one codebase? - How do you develop for WP and Windows 8?
- 8. There's a new version of Windows Phone coming… - But what does this mean for developers? - What's new? - What's changed? - How do you upgrade an existing WP 7.x app? - How do you support WP7.x & WP8 with one codebase? - How do you develop for WP and Windows 8?
- 9. ?
- 10. Samsung ATIV S
- 11. Nokia Lumia 920 & 820
- 12. HTC 8-X & 8-S
- 13. what does this mean for developers? flickr.com/photos/69302634@N02/7111451171/
- 14. possibilities new better
- 15. more sales?... devices > apps
- 17. shared core with Win8
- 18. WinRT
- 19. WinPRT?
- 20. WP7 WP8 managed code managed code WP7 API WP8 API WinCE/Win32 WinPRT
- 21. compile in the cloud makes no difference to dev experience
- 22. WP7.X apps run unaltered
- 23. app distribution big changes and opportunities
- 25. In app purchase image
- 26. in-app payments the missing link?
- 27. “among the highest grossing revenue models” “comes out ahead of other revenue models in terms of per-app, per-month revenues” “monetizing 2.2 times more than apps without” http://www.visionmobile.com/product/developer-economics-2012/
- 31. app to app comms not share contracts
- 32. Groupon image
- 33. Facebook image
- 34. pass commands to apps and with speech launch
- 35. native code But no XNA
- 38. multiple cores makes no(?) difference
- 39. new screen sizes redesign for them
- 40. + WXGA & 720P 1280x768 15:9 1280x720 16:9
- 42. images you’ll want to do more
- 44. images beware hardcoding dimensions
- 45. images scaling down is better than scaling up
- 46. images Can impact XAP size
- 47. Tiles image
- 50. multi-tasking “improvements” no real details yet
- 51. removable SD cards intranet install
- 52. 50 & 180+ languages & countries
- 54. Nokia maps go offline
- 55. SQLite truly cross platform DB
- 56. Other changes? Control changes? New controls? Toolkit changes?
- 57. how do you upgrade an existing WP 7.x app? flickr.com/photos/babbletrish/528807399/
- 58. how do you support WP7.x & WP8 with one codebase?
- 59. WP7.X apps run unaltered …
- 60. 7.8 apps also run on 8
- 61. how do you develop for Windows Phone and Windows 8? flickr.com/photos/manicstreetpreacher/ 471712788/
- 62. "reuse code“ "recommend not sharing UI"
- 65. No magic bullet fork link files shared library #compiler directives
- 66. forking about pros cons • Easy to change one • Duplication without affecting others • Duplication • Duplication
- 67. missing link pros cons • I think it’s awesome! • Lots of people don’t like it • Only one copy of code • Easy to extend – Partial classes & methods
- 68. sharing libraries pros cons • Single copy of code • Only LCD functionality • All related code in one • Harder to extend place – Event based
- 69. #compile pros cons • One file • Still need to share that file • Can get very complicated
- 70. V V VM VM M
- 73. PREPARE
- 74. SDK coming “later this summer” – apparently
- 76. learn Win8 port your apps
Editor's Notes
- Won’t be offended if you think you’re in the wrong room and want to leave
- I do this all day every dayWP 2.5 years“mobile” >8 yearsDev >13 yearsBuilt lots of WP apps for big names companies (including MSFT)
- Done or at least looked at some WP7 development- Quick poll of who has made apps & who knows nothing- Smart enough to know to ask questions as we go
- This is what was promisedNo secrets – no broken NDAs ;)No code – again I won’t be offended if you want to leave now
- No commentPublic information+ informed assumptions based on public information ;)
- This is what was promisedNo secrets – no broken NDAs ;)No code – again I won’t be offended if you want to leave now
- To late in principle? – Can WP really catch up with other platforms?If I'm honest, in the last two and a half years I've been on the verge of giving up on Windows Phone maybe four or five times.The possibilities that Windows Phone 8 could bring left me excited.There was a 2 day developer event planned.OK so it was invite only and I wasn't invited but the possibility of what could be announced was still promising.Then it became a 1 day event.And finally it became a 2 hour press event.The focus was on high level features and no developer specifics.Initially this was disappointing but after some analysis there's actually a lot we can learn from this as developersTo late for developers?Would you have preferred less or buggy?They’ve always said they’d release when it’s ready and not be driven by external timescalesOf course it would have been nicer to have an SDK before now but it’s not going to make a real difference in the long run.To late in the year for sales?It’s different to previous yearsThe number of apps in the marketplace is no longer a real factor.Most of the big names are thereThere will be apps which make use of the new features and functionalityDevices are on track to be available by the important holiday sales periodsThere will be as yet unannounced features to drive newsworthy stories closer to launch (not months in advance) and avoid informing the competition of what they’re planningFeb - announce of existenceApril/May -SDK originally expected (based on previous years)June – WP SummitAug/Sept – 1st device detailsSept? – SDK hopefullyLate Oct? – first devicesExpectations based on pastwp releasesCompare with Apple/iOSNo right to indignation
- - do what couldn't before- do things better- provide a betterux
- Shared WinRT coreWill make code reuse easier : namespacesStill don't want a shared ui
- Shared WinRT coreWill make code reuse easier : namespacesStill don't want a shared ui
- CinC = perf improvements in running apps - as no jitting and ability to offer further optimisations in compilation Can we expect a change in XAML?Would XAML really be recompiled in the cloud?What about XAML loaded at run time? - surely that means the XAML won't change. Or apps will need to be altered. Maybe?Would/does it matter? Markup is on top of the managed layer which is on top of the native/OS layer - it's that that's changed
- means different XAML namespaces?RichTextBox.XAMLDynamically loading styles, etc.
- And Win8 too?
- Now limits of the system won’t be a limit or an excuse on how you can’t monitise apps
- If it's just basic sharing than that'll be ok.It's something else we can do from/with/in an app If it gives us a helpful, simple managed way to implement data storage, key manipulation and encryption then we could do some much more exciting stuff
- Ignore native code for nowWe don't know enough about what we'll be able to do with it beyond DirectXWe don't know how it will integrate with the managed stackNative CodeMore big names apps is better for the platform = more salesLong term it's the alternative to XNA and provides cross platform capabilities (not forgetting MonoGame though)Native & XAML mix (like XNA & Silverlight?) - So Native knows about Managed lifecycle?“Windows Phone 8 will support three approaches to developing apps. First, as is the case today, a developer will be able to choose to build his or her Metro UI in XAML. Second, developers will also be able to use Direct3D to build their game UI or to port over existing UI framework libraries. Third, Windows Phone will support HTML5 development using standards-based web control, which will allow developers to reuse their HTML5 content. Last, developers will be able to use any or all of these approaches in combination to create or port back and forth apps”
- Emulator is Hyper-V image so will need Win8Will target 7.8 & 8
- Multiple cores provides no developer opportunity : still need to consider user experience and responsiveness — don't slow down the ui threadKeep doing things asynchronously
- Fragmentationvs multiple screen sizes
- Autoresize if don't do anything Show auto adjusted screenshots from top apps720P --- stretch or letterboxingletterboxing 80px
- Autoscaling won't affect fonts or vectors but will affect bitmapsAssume multiple images defined as per MSAsimage.pngimage.scale-140.pngimage.scale-180.png
- Learn about relative sizing & how stretch works – beware what blend does (it likes adding specific values)
- + hi-res marketplace image????
- Remember retina display versions
- Show fake app
- Current – 173xSmall - Med - 210Large -
- Improvement != fundamental change- probably not the end of tombstoning and FASIncreased functionality with background agents (access to location)
- SD cards : Need to think more about disk space and file access. Does this give us shared data? Need to consider the consequencesAlternative marketplaces? Unlikely?... Based on WP7 security principles
- marketplace improvements (rewritten)
- Better embedded contentphoneGap a viable solution?Js speed 4x faster2x html5 capabilitiesRender time?
- Performance progress bar | tilt | other toolkit controls*** End of Feature list ****> How upgrade?
- You may not want to but it’ll be very easyAnswer the next question at the same time
- As mentioned earlier – you may not want to
- Probably want to upgrade 7.x apps to 7.8 to support people with existing devices
- “strong similarity to Windows 8”, “easy to port”
- Different solutions for: different problems; different teams; personal preferences
- Good for lowest common denominator functionalityNot suitable for code with 3rd party dependencies
- Speculate at will. September? Build?
- create an opportunity for promotion:- Better- Different- Demonstrate the platform
- Get familiar with itYou said you were interested anywayGet familiar with VS2012Dev Camp + AppLab > Store + rewards