Your SlideShare is downloading. ×

In-house post-PC apps for the enterprise

115

Published on

Published in: Technology, News & Politics
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
115
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
1
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. In-house Post-PC Appsfor the EnterpriseMatt Baxter-ReynoldsThe Platform, May 2013
  • 2. Agenda• Post-PC in context• Building solutions• Delivering solutions• Q&AIn-house post-PC apps for the enterprise 2
  • 3. Platforms discussed today• We’ll be looking at…– iPad– Android tablets– Windows tablets• Not BlackBerry…– PlayBook is not current OS wave• Most of what we discuss applies to bothsmartphone and tabletsIn-house post-PC apps for the enterprise 3
  • 4. Post-PC in contextIn-house post-PC apps for the enterprise 4
  • 5. Post-PC devices• “Post-PC” devices refers to currentgeneration tablet and smartphone“compute devices”• Apple’s last reported figures were 19.5million iPads sold in the last quarter…– That’s 2.5 iPads sold each second– Up from 12 million like for like• We know people are buying them!– But what are they using them for?In-house post-PC apps for the enterprise 5
  • 6. Personal use of post-PCdevices• Smartphones and tablets are“relationship-centric”…– Connects you to the people and things thatare important to you– Based on “ubiquitous computing” (“ubicomp”)concepts laid down in the 1980s– Original concepts includes “tabs”, “pads”, and“boards”– Always around, but in the background– Not about workIn-house post-PC apps for the enterprise 6
  • 7. Business use of post-PCdevices• Computer systems are about commercialefficiency…– “We can manage our cash flow better if we havecomputerised credit control”• Therein lies the tension…– Post-PC devices don’t really make much senseagainst commercial operations• Except for niche, traditional mobility requirements– The trick is to apply relationship-centric thinkingto commercial operations• B2B – spend profiling• B2C - M&S shopfloorIn-house post-PC apps for the enterprise 7
  • 8. Typical use of post-PCdevices in business• Classics…– Email– Managing a diary– Web browsing– Document browsing– Navigation (finding meetings)• Newer ideas…– Skype– Evernote/OneNoteIn-house post-PC apps for the enterprise 8
  • 9. Replacing the PC?• Depends on the audience…– Common to find that C-level executives can do it– Specialist jobs can…• But typically only those in traditional mobility space– There are likely others• The intention is never to replace the PC– This is a key part where people get confused– Deliver one tool for commercial efficiency– Deliver another tool for relationship efficiencyIn-house post-PC apps for the enterprise 9
  • 10. What do people mean bythe “death of the PC”?• They mean the PC stops being importantto the consumer space...– The consumer “compute device” market getsbigger compared to enterprise– The enterprise market therefore becomesniche– …but not necessarily smaller in and of itself• Thus the PC is not “dying”…– It likely does not find a new life outside ofcommercial efficiencyIn-house post-PC apps for the enterprise 10
  • 11. Building solutionsIn-house post-PC apps for the enterprise 11
  • 12. General shape of the problem• Identify opportunities that arerelationship-centric…– Don’t be lulled into thinking of the tablet as aterminal• Device types…– Enterprise-supplied– BYODIn-house post-PC apps for the enterprise 12
  • 13. Available delivery technologies• Native code– Developers have to write apps in the toolset that thevendor prefers they use• HTML5/Hybrid apps– Developers build a packaged website– PhoneGap, Titanium are classic examples of thisapproach• Shimming– Xamarin is a classic example of this approach– Developers build apps using an abstraction layer abovenative code• Virtual desktop infrastructure (VDI) or Web apps– Treating the tablet as a PC-like consoleIn-house post-PC apps for the enterprise 13
  • 14. Native code defined• iOS– Xcode, Objective-C, Cocoa Touch• Android– Eclipse, Java, Android SDK• Windows 8/Windows RT– Windows Store apps– Visual Studio– WinRT and C# – this not .NET– HTML5/JavaScriptIn-house post-PC apps for the enterprise 14
  • 15. Shimming• Xamarin is the classic example• Principle here is to remove a chunk of the learningcurve...– Still the vendors API– But a different language and related tooling• The advantage...– Less time to spin up– More commonality across platform– Close to the platform owners vision• The disadvantage– Dependence on a third-partyIn-house post-PC apps for the enterprise 15
  • 16. The Native Windows Wrinkle• Microsoft’s vision is…– Metro-style (“Modern UI”) aesthetic– Windows Runtime (WinRT) API• However, if you avoid Windows RT (ARM)devices…– You just have a normal Windows client– Run anything on it as you would normally doIn-house post-PC apps for the enterprise 16
  • 17. The choice• The basic decision is which of those fourpaths you choose...o Each path comes with different velocity oninitial developmento But, each path comes with development debto You can blend the approaches to suit yourneedsIn-house post-PC apps for the enterprise 17
  • 18. The additional complexityof cross-platform• Enterprise hasn’t had to worry about thismuch• Cross-platform is about both what you needtoday, and what you need tomorrow...– So be careful if you only need iPad today• Very difficult to achieve– There is virtually no crossover between toolsets– Code has to be re-crafted, re-tested multipletimes• Be wary of "magic bullets"In-house post-PC apps for the enterprise 18
  • 19. Native code – Pros/Cons• Proso Closest to the vendors visiono Best performance, best experience• Conso Difficult to get up to speedo Creates complex skills requirementsIn-house post-PC apps for the enterprise 19
  • 20. Hybrid apps – Pros/Cons• Proso Can reuse existing skillso Very fast to get something working• Conso Almost impossible to build anything complexIn-house post-PC apps for the enterprise 20
  • 21. Shimming – Pros/Cons• Specifically...o Xamarin, as this has the only mature product in thisspace• Proso Can take a lot of enterprise skills over (C#)o Very close to the vendors original vision of how thetooling should be• Conso Could be introducing debt that you dont needIn-house post-PC apps for the enterprise 21
  • 22. VDI/Web – Pros/Cons• Pros– Cheap and easy• Cons– Very poor user experienceIn-house post-PC apps for the enterprise 22
  • 23. The particular problem withhybrid apps• The perception is that this is a sensible idea...– All of the pieces are in the right place– The reality is that the tooling is horrible...• Totally out of step with the vendors vision• Great feedback initially...– Gives the impression of progress at first– Like running into glue shortly after– Very hard to get across the finish line• The cross-platform argument is not good enoughIn-house post-PC apps for the enterprise 23
  • 24. Examples of hybrid appproblems• Functionality…– Dependent on the functional set in the library– Have to write plugins to fill gaps…• Might as well just write native• Performance…– Dependent on JavaScript performance– Might be OK on device A, awful on device B– Very little you can do about thisIn-house post-PC apps for the enterprise 24
  • 25. The problem with VDI• VDI assumes the tablet is a PC…– …which misses the point as the tablet is a post-PCdevice– VDI imposes commercial efficiency onto a devicethat’s about relationship efficiency– Also problems with the UI• As a result, you get a tremendously bad userexperience• Use sparinglyIn-house post-PC apps for the enterprise 25
  • 26. Is learning the native toolsetworth the pain?• The native toolsets gives absolutely thebest possible results• But they are hard to use...o Different/weird• From first principles people gravitatetowards cross-platform...o In the long-term, "going native" might be bestIn-house post-PC apps for the enterprise 26
  • 27. Blending• In-house apps you have more control ofthe audience…– Enterprise supplied iPads, variety of BYODsmartphones, or…– BYOD policy supports Android and iOS only,etc.• Your approach could be to blend…– Target primary platform(s) with native (orshimmed)– Web or VDI deployment to secondaryIn-house post-PC apps for the enterprise 27
  • 28. Private app delivery• “Sideloading”– As opposed to “downloading”• iOS– Special enterprise program– $300 a year• Android– Turn off device security, install from APKIn-house post-PC apps for the enterprise 28
  • 29. Private app delivery onWindows• Windows Store apps– Sideloading enabled as part of volumelicensing– Alternatively, buy a “sideloading key”– Windows RT• Has to be pushed with Windows Intune– Windows 8• Pushed with Intune, or PowerShell, etc.• Windows Phone– Has to be pushed with Windows IntuneIn-house post-PC apps for the enterprise 29
  • 30. Delivering solutionsIn-house post-PC apps for the enterprise 30
  • 31. What does BYOD mean?• “Bring your own device”– But is that actually what’s happening?• The reverse is true…– Employees are taking your data to their device• Sociologically interesting…– Employee now has data wherever and“whenever”they areIn-house post-PC apps for the enterprise 31
  • 32. Work/life balance• Checking your email when out for dinnerwith your spouse…– Used to be technically and sociologicallycomplicated– Now it’s just sociologically complicated• How can you take advantage of peoplewho perform outside of the boundaries ofwork?– Work/life balance is not structured in anobvious wayIn-house post-PC apps for the enterprise 32
  • 33. What does MDM do?• Enterprises were tooled up to manage Windowsdevices…– And mobile arrived!– First purpose is to close that gap– Second purpose is to provide for BYOD• Features– Provisioning– App distribution– Document lockers– SecurityIn-house post-PC apps for the enterprise 33
  • 34. MDM pricing• About £5 per device per monthIn-house post-PC apps for the enterprise 34
  • 35. Provisioning with MDM• The process of getting the device onto thenetwork…– Have to install a bootstrapper– Apply policy, e.g. encryption, passcode– Automatic setup of email profiles,VPN profiles etc– Automatic installation of apps• If you’re buying enough, the bootstrappercan be installed by the retailerIn-house post-PC apps for the enterprise 35
  • 36. App distribution with MDM• Typically follows an “app store” metaphor• Functions…– Whitelisting– Blacklisting– Required apps– Optional apps– SideloadingIn-house post-PC apps for the enterprise 36
  • 37. Document lockers with MDM• Secure container for managing documents– Sync with in-house systems• SharePoint, file shares– Remote wipe– Additional encryptionIn-house post-PC apps for the enterprise 37
  • 38. Security with MDM• Enforced encryption• GPS tracking• Remote wipeIn-house post-PC apps for the enterprise 38
  • 39. How mature is the MDMmarket?• This market is now very mature for iOS andAndroid…– AirWatch– MobileIron– Good Technology• It is less mature for Windows andBlackBerry…– Windows Intune• Windows Phone, Windows 8, Windows RT– BlackBerry Enterprise Services 10• Nee “Mobile Fusion”In-house post-PC apps for the enterprise 39
  • 40. BlackBerry Secure Work Space• Interesting new product this year…– BlackBerry’s trick was always that devicesconnect behind the firewall– BB10 devices with BES10 do this today– “Secure Work Space” will let iOS and Androiddevices do this tooIn-house post-PC apps for the enterprise 40
  • 41. Q&A• Matt Baxter-Reynolds (mbrit)– Twitter: @mbrit– Email: matt@theplatform.ioIn-house post-PC apps for the enterprise 41This work is licensed under a CreativeCommons Attribution-ShareAlike 3.0Unported License.

×