Detroit Labs Spring 2013 Mobile Update

Talk to Microsoft Detroit on what's up with mobile.

Transcript

1. WHAT’S UP WITH MOBILE? a check-in with Detroit Labs
2. Nathan Hughes, @ndh313 Co-Founder Podcaster Beatmaker Parenteer Improviser Gamer
3. Detroit Labs
4. Let’s talk about
5. Let’s talk about State of the App Dev World
6. Let’s talk about State of the App Dev World Demand for Apps
7. Let’s talk about State of the App Dev World Demand for Apps Complexity of Apps
8. Let’s talk about State of the App Dev World Demand for Apps Complexity of Apps
9. Let’s talk about State of the App Dev World Demand for Apps Complexity of Apps Windows 8 Mobile Development
10. State of the App Dev World
11. The global apps business is expected to make $25 billion in revenue (in 2013), up 62% from a year ago. - Gartner.
12. Per Flurry Analytics, people are spending an average of two hours a day on apps, almost half of that game playing.
14. At the end of 2012, the average price paid for an app in the Apple store was $3.18 on an iPhone and $4.44 on an iPad, according to Distimo. That compares with an average price of $3.06 in the Google Play store. - Wall Street Journal, 3/11/2013
15. Fragmentation
17. Based on Android devices that have accessed Google Play within a 14-day period ending on March 4, 2013. http://developer.android.com/about/dashboards/index.html
18. http://developer.android.com/about/dashboards/index.html Based on Android devices that have accessed Google Play within a 14-day period ending on March 4, 2013.
19. Lucky iOS doesn’t have those problems.
22. Immediate adoption of new updates is faster on iOS, but stragglers still hang on.
23. iPhone 3GS iPhone 4 iPhone 4S iPhone 5 iPod Touch 3rd Gen iPod Touch 4th Gen iPod Touch 5th Gen iPad iPad 2 iPad 3rd Gen iPad 3rd Gen Retina iPad 4th Gen iPad 4th Gen Retina
24. Moving on to demand, or as we say
25. Does anyone actually want these things?
26. Thank goodness, yes.
27. Someone has to make those apps that are capturing $25 Billion in App Revenue this year.
28. We’re moving past the junky toy app phase.
29. (I guess the world only needs so many fart apps)
30. And while marketing is still looking for that big splash app...
31. IT is starting to spend, so we’re getting back to business.
32. HOW DO I - maintain my high falutin’ brand standards? - get this data into my enterprise crm? - measure the value I’m getting? - connect this user to a purchase? - keep this data secure?
34. We know how to figure that stuff out.
35. Moving on to App Complexity, or
36. Let’s build some things.
37. Native Development is still king.
38. Top Brands + Clients want
39. Top Brands + Clients want Responsive Experiences
40. Top Brands + Clients want Responsive Experiences Beautiful Designs
41. Top Brands + Clients want Responsive Experiences Beautiful Designs Every New Feature
42. You know, like apps that use Camera GPS Accelerometer Offline Usability Local Storage
43. But cross-platform is trying to catch up.
45. And developers want other languages to develop in.
46. And developers want other languages to develop in.
47. And developers want other languages to develop in. their favorite
48. Because NO ONE LIKES (Objective-C, Java, Android SDK, C#)
49. And EVERYONE LIKES (Ruby, Python, Java, C#, JS, HTML5)
50. Yeah, sure, I guess?
51. I give it three years.
52. What about all our modern things?
53. Build Automation, good gravy.
54. Continuous Integration, good gravy.
55. Continuous Deploy, good gravy.
56. Changing Channels
57. What about talent?
58. New developers make good mobile developers because
59. pretty much every mobile app turns into a beautiful user experience surrounding API calls to things that do real work.
60. RESTful persistence Salesforce leads eCommerce Payment Gateways Data aggregators Leaderboards and Achievements
61. Experienced developers make good mobile developers because
62. the difficult parts of mobile app development are not mobile related, but computer science related.
63. Caching Performance Optimization Network Optimization Concurrency Build and Deploy Engineering Data Security
64. So the problem isn’t finding the right people.
65. It’s asking the right questions.
66. Onward!
67. Windows 8 Mobile Development
68. Observations from Detroit Labs as we finish our first Windows 8 Mobile Project
69. Established design guidelines spell out best practices for nearly everything.
70. Strict design rules dictate best practices for nearly everything.
71. A minimal UI approach means a much greater focus can be put on what matters - content.
72. It's difficult to create a unique or memorable experience when you can't stray far from the design guidelines.
73. Clear standards make experience and app flow decisions easier to make.
74. Searching for answers on the internet is difficult, because of the numerous very similar platforms.
75. Consistency of app look and feel makes predicting user behavior a little easier.
76. Hard to test with users. Because, right now, it is hard to find users.
77. XAML layout code and native components can be easily changed to fit all kinds of needs.
78. XAML rendering exceptions and some other runtime exceptions read like Klingon (we don’t read Klingon).
79. Code files and assemblies can be shared across multiple projects, allowing a developer to create multiple platform products.
80. Networking requirements for the software emulator break the network NAT configuration rules for most corporate infrastructures.
81. Networking requirements for the software emulator break the network NAT configuration rules for most corporate infrastructures. EXTERMI-NAT!
82. I’d rather C# than Objective-C.
83. There is no way to disable the phone lock. 99.9% of the time we try to debug on the physical phone it is locked and stops the deploy.
84. Overall for us, a solid first time experience.
85. Questions? Comments? Stories? Jokes? Riddles?
86. Thank you. Nathan Hughes, @ndh313