kevin francis developing on windows devices arc33 2
TRANSCRIPT
Spark the future.
Kevin Francis
Developing on Windows Devices
ARC332
Introduction
Are you in the right room?This is an Architecture TalkThere will not be code.There will not be demos.There might be videos.
This is a talk about when to use devices from a business perspective.We’ll cover:• What to use when • How to design apps and services• The Universal Windows Application model• Hints and tips
AgendaPrinciples: Users, applications,
Windows 7, 8.1 and 10
The Windows device family:Windows Tablets, Windows Phones, Microsoft Band, Surface Hub, Interactive Digital Signage, Xbox One, Augmented Reality and Virtual Reality
Universal Apps
Communication and Architecture
About Me30 years’ experienceDeveloper from Windows 1.0 to Windows XPArchitect from Windows 95 to Windows VistaManager from Windows Vista to Windows 8.1
MVP for Architecture for five years to 2010
Now CEO of Wild Mouse, a new kind of partner, very focused on devices
Devices for public, etc.
The Browser is Dead
Long live Apps!
Follow your users…
But actually read the data and think carefully.
Tablets and Phones
Let’s talk costs.
The costs aren’t in IT guys really. Let’s talk about what architecture decisions are really costing your business.
The Browser should be dead.
Consumer behaviour is also driving internal demands.
Productivity and mobility are big drivers.
Windows XP, 7, 8 and 10
Think big picture. Consider culture shock.The SP1 fallacy is just that.
The Windows 10 Upgrade
What do you get?
Q: Who is mobile?
A: Almost everyone.
Anyone that goes to meetings, is in customer service, is in sales or takes work home.
A laptop is not a desktop.
And it probably shouldn’t be a laptop.
Consider the productivity of a convertible with a pen.
Computers are not productivity.
And people aren’t born knowing how to use them…
Why Apps are different now…
Mobile devices capabilities.Enterprise app stores.Compartmentalised installation and operation.Easy sharing and integration.
So we need apps…
To BYOD or not to BYOD, that is the question.The case for the SOE.The case for no SOE.
Building SOE Apps
Native development.Universal apps.UX is king. Resizable.The return of client-server computing. Without the pain.
Building BYOD Apps
Only build them once.Use tools like Sitrion ONE, Xamarin and so on.
Architectural Principles
Make them work offline. Syncing is critical.Store data and content in the cloud, not on the device.Use the capabilities of the device. Especially the camera and pen.
Surface Hub
An amazing device4K, highly responsice touchscreen. Many, many, many points of touch. Pens!Inbuilt PC, audio, conferencing, NFC, networking.Just plug in and go! Well, sort of…
Collaborative Devices
Surface Hub is a big, beautiful, multi-user screen.It is not a big tablet!Interaction and UX design is critical.
Building for Surface Hub
Just Windows 10 apps.Reuse the plumbing and some logic.Build the UI specifically.It’s worth the work!
Interactive Digital Signage
Like Surface Hub, but not…
Long life, commercial, large touchscreens.Much cheaper than Surface Hub and more robust.Not as responsive to touch, not collaborative
Uses
Employee engagement. Team messages.Visitor sign in.Retail, hospitality, etc.Connectivity is important for customers.
Building Applications
Best to build Windows 10 apps.Design apps especially for large screens.Take touch sensitivity into account (don’t expect too much)
Kinect
Still magic…
Lets the computer see in 3D.Adds excellent voice control.Great where the computer can't be touched. Great where you need to watch or respond to people.
Technology.
It isn't really too hard to build Kinect apps.Kinect for Windows 2.0 device is needed.Applications run on the desktop (not as apps).
Also
Allow for the learning curve. Design interactions carefully. Combine with touch where possible.
Xbox One
Not just a games console.Much more than 70% of time on Xboxes is spent in apps – mostly video.The average user is over 40, and frequently female.Xbox has a unique position in many homes.It therefore provides a unique opportunity.
Developing for XboxIs not overly difficult, but is complex too.Yes, It is .Net. It is a lot like Windows desktop, but not exactly.The UX is subtly, but significantly different.Certification has always been a very big deal.
Virtual Reality
Oculus is an honorary Microsoft device.Virtual reality does have its places in the real worldWorks where you want to put the user in a different location.Travel, real estate, crime scenes, etc.
Conclusion
Productivity is the keyUnfettered user experiences trumps IT concerns.True BYOD carries too many hidden costs though.Right devices for right scenarios. Talk to the business.Think about non-traditional devices.
The Common ThreadsUnified Windows Apps really do work across all devices.Unity + Unified Apps is the key for anything really interactive.
Q & A
Complete your session evaluation on My Ignite for your chance to win one of many daily prizes.
Continue your Ignite learning pathVisit Microsoft Virtual Academy for free online training visit https://www.microsoftvirtualacademy.com
Visit Channel 9 to access a wide range of Microsoft training and event recordings https://channel9.msdn.com/
Head to the TechNet Eval Centre to download trials of the latest
Microsoft products http://Microsoft.com/en-us/evalcenter/
© 2015 Microsoft Corporation. All rights reserved.Microsoft, Windows and other product names are or may be registered
trademarks and/or trademarks in the U.S. and/or other countries.MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY,
AS TO THE INFORMATION IN THIS PRESENTATION.