📚 Framework-Driven Development

updated 7 days ago; latest suggestion 7 days ago

For me and my teammates, as we are working on a big mixed (Objective-C and Swift) project that constantly grows, it gets harder and harder to work with constantly increasing codebase - incremental build times are increasing with each new feature, which makes us simply staring at Xcode/AppCode for longer and longer time. This lead us to rethink the way we are building our app and we've decided to try out separating our app into frameworks, and when possible, even into static libraries. This has opened our eyes on the spaghetti-code problem that we had here and there, showed us how dependant different modules from each other are, even though that they shouldn't be. This has improved our code-health and separation of concerns.

I would like to dedicate this talk to show approaches of decoupling you codebase into different frameworks, difficulties that might arise while separating your codebase between 2 and more frameworks and ways to solve them.

Tooling

This talk will use default Xcode as well Cocoapods in order to show how Pods can be integrated into frameworks.

Suggestions

  • The proposal author responds 7 days ago

    I have just updated this proposal, thanks for your input!

  • 007dca74c613a8f4ab1ed47c7562a1cae68df25a?size=100x100 007dca74c613a8f4ab1ed47c7562a1cae68df25a suggests 7 days ago

    What approaches? What tooling? Pros and cons of this approach?