How to modularize an iOS app

October 8, 2014

This is the first post of a serie which will try to make you through the process of modularizing an existing iOS app.

We will be using (of course?) Cocoapods. A great introduction is the blog post Using CocoaPods to modularize a Big iOS App by Anthony Roldan at Hubspost's blog.

Here's some questions we will try to address through this serie:

  • How coupled are the existing classes ? (aka how big is the spaghetti plate ?)
  • Should we think by screen or by layer ? Both ? Neither ?
  • How big the toolbox (utility classes commons to many screens) should be ?
  • How do you begin ? Taking a big dive and go for the most important screen or begin at the suburbs of your app (I guess we can all answer to that one right now... but maybe not)
  • How do you do that in an app being shipped every 4 to 6 weeks ? Of course you will need heavy testing to prevent any major crash but how can you minimize the burden on the other developers' productivity ?
  • Won't having a pod for each screen/layer/brick slow down the pace of development ?
The first "real" post will try to answer the first two questions :)