Framework based architecture using Cocoapods

A introduction to our CHECK24 iOS app architecture approach for maximum speed and individuality for all products and company units.

Transcript

1. let architecture: [Framework] stefan@mayer-popp.de
3. Holding Travel Insurances Energy Rentalcar Shopping Many more…!
4. Holding Travel Insurances Energy Rentalcar Shopping Many more…!
5. Holding Travel Insurances Energy Rentalcar Shopping Many more…! App
6. Situation 900 Source files in Swift
 200 Source files in Objective-C 25~ full-time iOS developers

7. Problems Fast growing code base Long compile times Loosing days for merging Lower code quality
9. why?
10. Files 225 450 675 900 Compile time 01:30.017 03:00.035 04:30.053 06:00.070 12.2.2015 22.9.2015 23.11.2015 22.12.2015 22.1.2016 8.2.2016 Compile time / file count
11. Files 500 1000 1500 2000 Compile time 23:45 47:30 1:11:15 1:35 12.2.2016 12.4.2016 12.6.2016 12.8.2016 Forecast
12. Files 350 700 1050 1400 Compile time in seconds 07.500 15 22.500 30 100 files 300 files 501 files 1000 1300 Class test
13. Problems Long compiler argument list Path names No dependency check Excessive use of globals
14. Problems Long compiler argument list Path names No dependency check Excessive use of globals Waiting up to 300h per month
16. Big picture
17. External Another product Product B The product Core Plugin UI Components Product A APP Initial architecture
18. What is our goal? ⏱ Fast compile times Strict plugin architecture Technical separation Better testability ♻ Reusable components
19. Product B Product D Product A Core Plugin UI Components Product C New architecture The APP
20. Holding Travel Insurances Energy Rentalcar Shopping Many more…! App
21. Holding Travel Insurances Energy Rentalcar Shopping Other verticals Responsibility
22. Frameworks?
23. Frameworks A framework is a hierarchical directory that encapsulates shared resources, such as a dynamic shared library, nib files, image files, localized strings, header files, and reference documentation in a single package.
24. Uh, sounds great? 
 What does that mean?!
25. Framework magic Frameworks group related, but
 separate, resources together A framework can include any relevant 
 header files and documentation It shares the application context Frameworks can include a wider variety
 of resource types than libraries
27. CORE pod pod pod pod pod pod pod pod Responsibility
28. Framework based App Core Plugin Framework Pod Product A Umbrella App
29. Framework based App Core Plugin Framework Pod Product A Umbrella App
30. Framework based App Core Plugin Framework Pod Product A Umbrella App
31. Framework based App Core Plugin Framework Pod Product A Umbrella App
32. Framework based App Core Plugin Framework Pod Product A Umbrella App Core Plugin Framework Pod Product B Umbrella App
33. Framework based App Core Plugin Framework Pod Product A Umbrella App Core Plugin Framework Pod Product C Umbrella App Core Plugin Framework Pod Product B Umbrella App
34. Framework based App Core Plugin Framework Pod Product A Umbrella App Core Plugin Framework Pod Product C Umbrella App Core Plugin Framework Pod Product B Umbrella App
35. Framework based App Core Plugin Framework Pod Product A Umbrella App Core Plugin Framework Pod Product C Umbrella App Core Plugin Framework Pod Product B Umbrella App
36. Framework based App Framework Pod Framework Pod Framework Pod Framework Pod Core Plugin UI Components The APP
37. All in one repo Company git iOS
38. git
39. git
40. git-igitt
41. git
42. git-ar hero
43. New structure Company git The App Product A Product B A shared framework
44. Workflow Product A framework v1.00 CI v3.11 git push git tag Podfile pod install
45. Workflow The 
 App Product A v1.01 Product B > v1.2 Externals Podfile CORE = v2.4 Components = v1.3
46. source 'https://git.your-company.de/CocoaPods/Specs.git' platform :ios, '8.0' use_frameworks! target "TheApp" do pod 'core', '>3.11' pod 'uicomponents' pod 'productA', '>=0.34' pod 'productB', '1.0' pod 'greaterProductC' end Podfile
49. Problems, 
 again… Mixed code Objective-C code Scopes Your timeline
50. Pro’s Small project footprints Binary delivery is possible Awesome compile times, again Strict namespaces Reuseabilty No single project anymore! Future save architecture
51. Con’s Critical parts of the existing app will be rewritten Scopes need to be defined Use of C libraries breaks often No shared assets within IB Binary dependencies do not work in frameworks (e.g. HockeyApp)
52. Daily cons Every checkout implies pod update Other products are less visible Complex versioning and release management Missing version updates leads to uncompilable Apps
53. Unus pro omnibus, 
 omnes pro uno No product x specific code in core 
 components No centralized classes for everything Think big and small Communicate
54. Long-term alternatives We don’t know one yet... you?
55. Happy pod-tifying Feel free to share your ideas! and may the odds be ever in your favor stefan.mayer-popp@check24.de slack.swiftde.net Invite only
56. Happy pod-tifying slack.swiftde.net Invite only