Mobile Development for Web Developers

Presentation from Miracle Open World 2012. An introduction to mobile development for web developers.

Transcript

1. Mobile Development for Web Developers Jackson Harper @jacksonh http://speakerdeck.com/u/jacksonh Friday, April 20, 12
2. I am a new-ish mobile developer • Worked for eight years on the Mono Project • Lead mobile development at Entrada Health Friday, April 20, 12
3. I am not a clever man Friday, April 20, 12
4. Understand what makes a good mobile app Friday, April 20, 12
5. Good desktop, Web, and Mobile apps are fundamentally different. Friday, April 20, 12
6. VisiCalc Friday, April 20, 12
7. Excel Friday, April 20, 12
8. The Web! Friday, April 20, 12
9. Google Docs Friday, April 20, 12
10. Good Web Apps take advantage of the web Friday, April 20, 12
11. Mobile Apps are not just apps that fit in your pocket Friday, April 20, 12
12. Good Mobile Apps take advantage of hardware Friday, April 20, 12
13. Mobile Expense App • Use camera to take pictures of receipts • Use GPS to determine restaurant names • Use GPS to record mileage • Use clock to record time of expense • Use calendar and address book to determine purpose/ attendees Friday, April 20, 12
14. Sheet Music Friday, April 20, 12
15. Understand what hardware is available Friday, April 20, 12
16. iPhone 4S • 960x640 Pixel Display • 8MP rear camera (1080p Video) • 0.3MP front camera (480p Video) • Speaker • Two microphones (top and bottom) • Headphone Jack • 3 Axis gyro • Accelerometer • Proximity sensor • Ambient light sensor Friday, April 20, 12
17. Audio Routing Options • Apple headset • Loudspeaker • Top Microphone • Bottom Microphone • Bluetooth Device • AirPlay (out only) • USB Audio Accessories Friday, April 20, 12
18. iPad Microphones iPad iPad 2 Friday, April 20, 12
19. Brainstorming Friday, April 20, 12
20. Good Apps • Use Hardware • Integrate with existing services • Understand they are always with the user Friday, April 20, 12
21. Developing iOS Apps Friday, April 20, 12
22. iOS: It’s just Unix • Processes, Threads, Directories, Files • SQLite, plist files (xml), PNGs • Model, View, Controller Architecture Friday, April 20, 12
23. MVC • Models: Classes, persisted via SQLite • Controllers: Control App flow • Views: .xibs (iPhone and iPad) Friday, April 20, 12
24. App Lifecycle Active Inactive Background Friday, April 20, 12
25. Inactive State • Since iOS5 this is mainly just a transitional state • Will not receive UI events • Should pause execution • Can transition to Active or Background Friday, April 20, 12
26. Background State • Screenshot Taken • Release Resources, Save Data, Stop Timers • Approximately 5 seconds to complete • Background Tasks Friday, April 20, 12
27. Background Tasks • Can run for aprox ten minutes • Notified when time has expired • Aprox 2 seconds to respond to notification • App will be terminated if you do not complete Friday, April 20, 12
28. Waking from the Dead • Screenshot Displayed • Pending Notifications before UX Input • Important to monitor App Settings Friday, April 20, 12
29. Backgrounding is a fundamental concept and greatly impacts your application design Friday, April 20, 12
30. Notifications • Local: Scheduled • Remote: Pushed • Icon • Sound • Badge Count Friday, April 20, 12
31. Push Notifications • JSON • Max 256 byte payload • Routed through Apples Push Notification Servers • “Best Effort” but not guaranteed Friday, April 20, 12
32. Push Notifications APNS Your Server Request Token Friday, April 20, 12
33. Push Notifications APNS Your Server APNS Token Friday, April 20, 12
34. Push Notifications APNS Your Server APN Token + Identifier Friday, April 20, 12
35. Push Notifications APNS Your Server Push Notification Friday, April 20, 12
36. Push Notifications APNS Your Server Push Notification Friday, April 20, 12
37. Push Notifications APNS Your Server (optional) Message Request/Pull Friday, April 20, 12
38. Push Notifications APNS Your Server APN Token + Identifier APNS Token Push Notification Push Notification Request Token Friday, April 20, 12
39. Provisioning Profiles • Applications are signed with certificates • Signing “seals” an app and identifies it • App ID, Developer Certificate and permissions combine to make a provisioning profile • Three distribution models Friday, April 20, 12
40. • Likely not for you • Used by large companies to distribute in house apps Enterprise Distribution Friday, April 20, 12
41. Ad-Hoc Distribution • Up to 100 devices can be register per developer account • Can be distributed “over the air” • Useful for testing, sales demos, hot fixes • Distributed as .IPA files • Installation is a two stage process Friday, April 20, 12
42. IPA Files • Zip files that contain the app, its resources, and provisioning file Friday, April 20, 12
43. App Store Distribution • Requires Approval • Apps must be available via search • First submission: ~9 days • Updates: ~6 days • Updates can be held for release Friday, April 20, 12
44. App Store • Profound impact on development cycle • 12 day confidence • Dependencies on public APIs: • “Proxy” the API • Client side config Friday, April 20, 12
45. Rejection • Rejection is usually due to "marketing" • Do not ask for additional info • Fix or Appeal • Metadata fixes ~1 day, app fixes ~6 days • Appeals ~2 days Friday, April 20, 12
46. Things we take for granted Friday, April 20, 12
47. Networks • Poor 3G and WiFi connections • Proxies and strange security • Develop an offline strategy Friday, April 20, 12
48. Offline Strategy Nothing Cached Sync Friday, April 20, 12
49. Physical Access • Delete a file, update a row in a database, clear a cache • Command URLs: upload, delete, update row (execute SQL) • iExplorer: manually pull files off device Friday, April 20, 12
50. Testing • Mobile requires a different testing mix • Unit tests are still important • But compared to web dev, a higher percentage of functional and manual tests are needed Friday, April 20, 12
51. Three types of tests • Unit: low level • Manual: UX, functionality, sanity (scripts + use cases) • Automation: Load testing, Upgrade testing, Functional tests Friday, April 20, 12
52. Automation Testing • Load testing: file handles are freed, memory leaks, log file rotation • Upgrade Testing: ensure clean upgrade paths, ensure old versions work with new web services • Functional Testing: the app does what it is Friday, April 20, 12
53. Getting Started • iOS Tutorials: http://www.raywenderlich.com/tutorials • me: jacksonh@gmail.com twitter.com/jacksonh Friday, April 20, 12