Download to read offline
Uploaded byAlex Thissen
//customer/
The document summarizes Alex Thissen's perspective on announcements at Build about Windows 8 and development opportunities. It discusses Achmea's focus on being the most trusted insurer and how IT supports its mission. It outlines the new Metro interface on Windows 8 and opportunities for startups. Visual Studio will better support Metro development and ALM. HTML5 will be well supported but security risks exist. Overall, Microsoft has laid a solid foundation for Windows 8's success but there is much to learn for all parties.
More Related Content
//customer/
- 1. //customer/ A customer’s perspectiveon announcements at build Alex Thissen Principal Architect, MScc, Achmea alex.thissen@achmea.nl @alexthissen
- 2.
- 3. About Achmea • Insurancecompany • Achmea vs Achmea IT • Mission: “Meest vertrouwde verzekeraar” • “Ondernemen met IT” as a vision
- 4.
- 5.
- 6. Forms factor galore •ARM sweet spot • Competitive pricing
- 7. Revolution of Metro Touchfirst Consistent UI Web of Apps
- 8. Audiences for Metro Metrouser • Home user • Casual gamer • Commuter Hybrid user • Two modes: touch OR keyboard • Tablet on move • PC when docked Productivity/ Power-user • Keyboard and mouse • Desktop Apps
- 9.
- 10. Old versus newworld
- 11. A different Windows(Runtime) Language projections
- 12. Strategy with WinRT •Single runtime for all languages • Separation by metadata • Pushing .NET BCL into OS • Cleaning up “beauty flaws” from past
- 13. Reading between thetiles Windows Metro? Full version for ARM? Balance found?
- 14. Safe apps • WinRTsandbox • User consent • Distribution via Microsoft Store
- 15. Microsoft Store • Familiarparadigm • Customers regain trust in app quality and installation • Developers might feel different • Strict rules • Tooling to check compliance will be available • Only ad space for Desktop apps
- 16. Business opportunity • Lotsof potential for startups • 450M Windows licenses • 90% revenue by 5% of app developers • Succes of store and platform defined by apps • Conditions are met (tooling, deploy, medium) • Achmea opportunity for end-customers • Corporate store?
- 17. Observations on VisualStudio 11 • Metro apps and WinRT first class citizen • Alignment and shipping with Windows 8 • Parity for languages • Absorption of Power Tools and Feature packs: more productivity
- 18. Visual Studio ALM •TFS gets more focus on Agile and Scrum • Agile aligns well with MSCC • Closing loop with Ops and Stakeholder • Missing security tooling
- 19.
- 20. Future for developers Newfor everyone
- 21. Revival of C++ •C++ meets C# • Required for Metro DirectX development • Remains choice for speed, control less so No reason not to switch Few reasons to switch
- 22. HTML 5 andMetro • Great framework and tooling support • Reuse of assets • Create WinRT enthusiasm with web devs
- 23. Metro Internet Explorer •No plugins in Metro style IE • Web is not ready for large scale HTML5 • Reduced usability of websites
- 24. New possibilities withHTML 5 • Lot of focus on markup tags • Less for • Workers • Sockets • Implemented in .NET Framework 4.5
- 25. Risks of HTML+ WinRT • Takes XSS attacks to a new level • Beter term would be RSI? (Windows Runtime Script Injection) • Tooling to support is essential
- 26. SharePoint 2010 • Startup •Performance
- 27. Windows Server 8benefits • Easier virtualization • Via network and live migration • Windows 8 Server closer to Azure • Transition possibly easier • Incorporate lessons learned from Azure Continuous Availability Cost Efficiency Management Efficiency
- 28. Identity and AccessManagement • Essential part of GIA Infrastructure • ADFS 2.1 inside OS • .NET even more claims-aware • Policy based ACLs • Claims from devices
- 29. Future of gaming •Lots of developer support • Targeted at DirectX (and XAML) • Important steps in tooling • C++ required
- 30. • Targeted atMetro, Desktop and Xbox360 • Power and control • Steep learning curve • Targeted at Windows Phone, Xbox360 and Desktop • Easier to learn • But, no Metro
- 31. Closing thoughts • Microsofthas a solid basis for success • Exciting times • Lots to learn for everyone • New possibilities and opportunities
- 32. Average reaction Customer AchmeaDeveloper Myself
- 33.
- 34. Thank you Reach meat Email: alex.thissen @achmea.nl Twitter: @alexthissen
Editor's Notes
- #6 iOS/Android and Windows 7 love child
- #8 Touch first, sensor aware Consistency of UX Web of Apps (OS is meer dan alleen bridge hardware, ook verbinden van apps) Safety by sandboxing, deployment, user content
- #9 Outside office employees End-customers Not so much for productivity user
- #11 Hard boundary between Metro and Desktop Balance in UI Old == legacy?
- #12 Language projections Modernized COM runtime, but does not look like it from languages Async all over the place Goodness not hassle
- #13 Preparations for next move?
- #14 New Windows Metro version? + ARM == Ipad killer Direction for ARM
- #15 http://articles.businessinsider.com/2011-08-24/tech/29984452_1_malware-android-market-app-store
- #16 Strict rules Deployment mechanism Advert space for Desktop apps Trust in application quality Hurdle to take
- #20 Silverlight .NET Framework XNA No, main technologies remain Yes, new/other frameworks to learn (as always)
- #21 3 archetypes Managed dev HTML designer/dev Hardcore C++ Unlike that switches will occur Onboarding of non .NET devs (focus widening from .NET to C++/HTML)
- #22 C++ meets C# (language + tooling) Still a more difficult language Needed for Metro DirectX development Hardly any movers Good to see evolution of language Remains choice for speed, control less so
- #25 Cannot make distinction when browsing to
- #28 HTML 5 .NET 3.5+ MVC Yet, there are possibilities plus options for backend IIS8 (startup, performance)