Ingredients for Mobile Success

Presented to the Dallas Mobile users group in September 2012 about some tips and tricks related to the mobile Web and native development.

Transcript

1. Ingredients for Mobile Success DalMob Conclave – September 2012
2. Hi. Chris Voss John Tornow @tophervoss @jdtornow
3. Get going Designing Building Shipping
4. Getting Started
5. Choosing a platform is still a difficult decision.
6. vs. Technologies you know Shared platforms Ubiquitous Rapid deployment No install needed Write once, test everywhere Mobile Web Faster Experiences are usually better Offline access Access device hardware App Stores Write everywhere, test everywhere Native
7. Your decision isn’t set in stone.
8. Choose a platform. Launch. Iterate.
9. Designing the Experience
11. Think mobily.
12. Think mobily mobilier.
13. Think mobily mobilier mobile.
14. Where will they be using your app?
15. Don’t just mirror an existing website.
16. Is this critical information the user needs right now?
17. Focus on the primary tasks
19. Make it obvious how to accomplish the tasks
20. Make it obvious what the user should do next
21. Make it obvious what the user should do next
22. Make accomplishing a task fun
23. Sweet! It looks just like the “Find My Friends” book I had growing up!
24. Developing for the Mobile Web
25. The “Modern” mobile Web is really complicated.
26. About 90% of “modern” mobile web is WebKit 6% 2% 89% 3% Opera WebKit IEMobile Other Source: http://gs.statcounter.com
27. It’s ok to assume WebKit. But don’t count on it.
28. 50% of mobile users abandon a page if it doesn’t load in 10 seconds or less.
29. Web page performance is crucial.
30. Don’t try to emulate native too much. Use the Web for what it is.
31. Avoid “all in one” frameworks.
32. Use CSS3 animations instead of JavaScript...
33. ...but fall back to JavaScript if necessary.
34. Limit your JavaScript frameworks
35. Overkill? jQuery & jQuery UI Backbone.js Underscore.js Sammy.js Spine.js Knockout.js Ember.js
36. Use only what you need with micro-frameworks.
37. jQuery > Zepto ~8.4k ~32k
38. Use intelligent caching and page loading with pushState.
39. pushState + Ajax = pjax github.com / defunkt / pjax
40. Use “retina” grade graphics sparingly, and only for those that need them.
41. Getting a native app off the ground quickly
42. CocoaPods is the best way to manage library dependencies in Objective-C projects.
43. An example Podfile: platform :ios, '5.0' pod 'AFNetworking', '>= 0.5.1' pod 'NSString-LOLSpeak' pod 'iCarousel', :head target :test, :exclusive => true do pod 'GHUnit' end
44. Networking for iOS and OSX http://afnetworking.com pod search AFNetworking
45. Networking/Object mapping for iOS and Mac http://restkit.org pod search RestKit
46. ZUUIRevealController pod search ZUUI
47. Facebook SDK http://developers.facebook.com pod search Facebook
48. http://cocoapods.org (sudo) gem install cocoapods
49. http://parse.com
50. Parse Data Browser
51. iOS PFObject *post = [PFObject objectWithClassName:@”Post”]; post[@”title”] = @”Hello World”; [post saveInBackground];
52. Android ParseObject post = new ParseObject(“Post”); post.put(“title”, “Hello World”); post.saveInBackground();
53. Free for up to a million API requests and a million Push Notifications a month
54. Easy Push Notifications for iOS and Android
55. User Account Management
56. In-App Purchases for iOS
57. parse.com
58. Ship.
59. “On-time isn’t cool. You know what’s cool? Early.”
60. Break down big projects into bite size chunks.
61. Ship something at least every 90 days.
62. Daily communication is required.
63. Change is inevitable, roll with it.
64. Thanks. ovenbits.com / presenting / dalmob