Building libraries for iOS — Going native (v2)

As the iOS community grows, code sharing becomes more and more important thing to discuss. In this presentation I'll share my experience of being a library vendor. I'll give an overview of dependency management approaches. In the "Going Native" part I'll explain why it might be a good idea to stay native and master your libraries manually.

Transcript

1. Building libraries for iOS Going native Alexander Dodatko 2014
3. The standard library saves programmers from having to reinvent the wheel. Bjarne Stroustrup http://bit.ly/1iqZ3JO
5. Code Reuse is Important
7. March 2008
8. http://engt.co/1pOLKH9
9. The fastest code is the code that reaches the market first
10. Nobody Cares
12. August 2011
17. pod install SomeAwesomeLibXYZ
18. Except...
21. Typical Workflow
25. Our own Busyness Logic
27. In-Place Editing
29. Modular Architecture Benefits Code Reuse Test Coverage Easier to Apply Changes
32. Going Native
34. --no-integrate
37. Not Just Library Target
38. #import <AFNetworking/AFNetworking.h> #import "AFHTTPRequestOperation.h" VS
39. #import "AFHTTPRequestOperation.h" For Implementation Files
40. #import <AFNetworking/AFNetworking.h> For Public Headers
41. Incapsulation
43. #import <AFNetworking/AFNetworking.h> #import <Foundation/Foundation.h>
44. Static Framework for iOS
46. <plist version="1.0"> <dict> <key>CFBundleDevelopmentRegion</key> <string>English</string> <key>CFBundleIdentifier</key> <string>org.ocmock</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundlePackageType</key> <string>FMWK</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>2.2.3</string> </dict> </plist>
47. Drag & Drop
48. Framework Search Path is updated by Xcode
49. Frameworks Reduce Compilation Time
51. Sharing Swift Code is Painful
52. Wrapper Obj-C Classes
53. swift -emit-module swift -emit-library
54. CocoaPods Makes you Care about Versioning
55. CocoaPods set Rules for Library Vendors
56. More Binary Pods In My Opinion
57. For Distribution For Development and Unit Testing
58. For You For End Users
59. Library Dependencies and Linker
62. Never Link Libraries into Other Libraries
66. All Testable Code Should be in libraries
67. Use Precompiled Headers Reduce Comping Duration
68. #ifdef __OBJC__ #ifdef __cplusplus // Objective-C++ headers go here #import "MyObjectiveCppClass.h" #endif // Objective-C headers go here #import <Foundation/Foundation.h> #endif #ifdef __cplusplus // Pure C++ headers go here #include <vector> #endif // Pure C headers go here #include <math.h>
69. Order by Dependencies
70. Library Vendor's Checklist
71. For Distribution For Development and Unit Testing
72. #import <AFNetworking/AFNetworking.h> For Public Headers
74. Do Write Unit Tests With best possible coverage you can afford
75. Deliver Binary Pods
76. Source Based Pods as a “Plan B”
77. Native Rulezzz Alexander Dodatko @dodikk88