Building modular Mac and iOS apps using Bundles

Using WHPluginService to reduce NSViewController/UIViewController complexity and tight coupling of your applications.

Presented at Sydney Cocoaheads in March 2014.

Transcript

1. Building  modular  applica/ons   with  bundles
2. whimsy whimsyapps.com
3. Op/que Fast  &  light  photo  management  for  Mac Get  it  now  from  op8queapp.com
4. Problems  with  building  Apps  on  iOS  and  Mac • NSViewControllers/UIViewControllers  get  massive  +  complex  quickly   =  harder  to  understand  +  merge   • Tight  coupling  makes  apps  hard  to  refactor   • Easy  to  be  lazy.  AppDelegate  all  the  things.
5. How  can  bundles  help? • Reduce  overall  complexity  of  your  applicaKon  by  making  it  modular   • Keep  NSViewControllers/UIControllers  lean  +  mean     • Allow  others  to  extend  without  having  to  understand  the  whole  app
7. Bundles • Bundles  encapsulate  code  and  resources   • Contains  resources,  object  code  and  Info.plist   • Info.plist  defines  the  Principal  Class.     • Typically  found  in  <App  Bundle>/Contents/PlugIns   • Read  Apple’s  Bundle  Programming  Guide
8. Building  your  first  bundle  loader
9. Structure Application Framework Bundles Plugin and controller protocols Classes that conform to protocols Controllers and other application code
10. Dependencies Framework Bundles Application
11. Dependencies Framework Bundles Application @protocol WHViewController @interface WHSomeViewController consumes WHViewController
12. Example  project
13. Bundles  in  Op>que
14. Resources • Apple’s  Bundle  Programming  Guide
 h"ps://developer.apple.com/library/mac/documenta7on/corefounda7on/ conceptual/c9undles/   • Plugin  loader  for  your  own  projects  (with  example)
 hTps:/ /bitbucket.org/whimsyinc/WHPluginService   • pod  ‘WHPluginService’  ‘~>  0.0.1’   • Ping  me  on  Twi"er  @i386