Open Source

Open Source components and tools are a major part of building great applications in the field of mobile computing and other programming platforms. This talk is an introduction to how to use, contribute to, and create your own open source components for others to use.

Transcript

1. Open Source An overview of why open source is key to building mobile software. By: Conrad Stoll, @conradstoll Architect, Mutual Mobile
2. How do you build an application?
3. How do I participate in the community?
4. Learning about Dependencies
5. Shared Problems Deserve Shared Solutions
6. What sort of problems?
7. Communication over a network Responsive User Interface Data Persistence Testing Dependency Management
8. Great Open Source software Very applicable to other people
9. Sometimes it takes multiple people To solve a hard problem
10. What can you do with Open Source?
11. 1. You can use it 2. You can contribute to it 3. You can make your own
12. 1. Using Open Source Open Source tools help you focus on the real work you need to do.
13. Focus on solving the key problems for your project.
14. Web Frameworks Django Rails Node Angular
15. HTTP Networking
16. AFNetworking
17. OkHttp
18. User Interface
19. Challenges Building User Interfaces
20. Animation Animation conveys meaning and makes your app more delightful.
21. Performance Interfaces should be fast and get out of the users way.
22. Facebook Immensely complex app Polished UI
23. Tools React ReactNative ComponentKit
24. Paper Different take on Facebook, with an amazing interface
27. Tools AsyncDisplayKit Pop Tweaks
28. Consistency Making an app feel familiar to users on the platform
29. MMDrawerController You know those side menus on iOS apps?
31. Super common problem Thousands of apps do this.
32. Super easy to use library to build a side menu Over 4000 stars on GitHub
33. Data Persistence
34. SQLite Used for...just about everything.
35. Realm Competitor to SQLite Partially open source, with a full company around it. Designed for Mobile!
36. MMRecord Serialization, between REST and Core Data
37. We were solving the same problem in all of our projects
38. Ridiculously easy to connect a web service to Core Data Used across many projects at Mutual Mobile and hundreds of other projects in the community.
39. Consider how you use Open Source dependencies
40. Dependency Injection Don't allow your database code to seep into your views.
41. Dependency Management Know what versions you're using and if they're maintained.
42. 2. Contributing to Open Source Are you using Open Source? What could you do to make it better?
43. Look at the libraries you are using. Do they have any problems?
44. XMPPFramework Multithreading and crashing problems Submitted updates to fix them
45. Urban Airship Super popular push notification provider
46. Fixed several issues with their SDK for iOS
47. How to contribute back?
48. STOP! Don't write code yet.
49. First Step: Identify the Problem Is the problem in the library, or with your implementation of it?
50. Second Step: Ask for Feedback (Before you write code!)
51. Third Step: Make your contribution easy to accept
53. Submit clean code Match the style of the library you're contributing to
54. Write tests if you're fixing a bug And of course, manually test the code yourself
55. Create beautiful programmer interfaces Think of developers as your users Eliminate typos, write documentation, think about your method names
56. So why should you contribute?
57. Improve the tools that you already use Part of being a good citizen in the developer community
58. Learn about how things work Open a library up and read it. Figure out how it works. Learn something new.
59. Build your Portfolio Contributing to open source is great practice. It's good for your career!
60. 3. Releasing Open Source Share openly Solve important problems
61. Have you seen the same problem twice? Do you have a solution for it? Bingo!
62. Make it Easy to Use The key to great open source is ease of use.
63. API Make it Intuitive Keep it Simple
64. Documentation Write detailed header documentation. Clearly explain how to use your library.
65. Examples Include examples of how to use your library.
66. Solve an obvious problem Make your library something that resonates with people.
67. MMWormhole
68. Inter Process Communication How do you share information between the watch app and the iPhone app?
70. Apple didn't provide a solution for this Left to developers to figure out how to do it
71. We Solved It! And we made it SUPER easy to use.
72. Shared with everyone Posted on developer forums Posted on Twitter
73. Used in Thousands of Apps Best way to communicate between iPhone and Watch app
74. Easily Extendable Updated to support watchOS 2
75. Final Thoughts
76. Living Reference Don't forget about your project Challenges with Swift
77. Water Cooler Provide a place for people to discuss common problems
78. Adapt and Evolve AFNetworking - Objective-C Alamofire - Swift
79. AFHTTPRequestOperationManager *manager = [AFHTTPRequestOperationManager manager]; [manager GET:@"http://example.com/resources.json" parameters:nil success:^(AFHTTPRequestOperation *operation, id responseObject) { NSLog(@"JSON: %@", responseObject); } failure:^(AFHTTPRequestOperation *operation, NSError *error) { NSLog(@"Error: %@", error); }]; Alamofire.request(.GET, "http://httpbin.org/get")
80. Summary: Use excellent tools
81. Give back to the community
82. Start something new
83. Thanks! conrad.stoll@mutualmobile.com @conradstoll