your own internal pods • Pods are 3rd party libraries and are not “silver bullets” • Revisit before shipping to production and use a checklist for accepting a 3rd party library • For more information visit http://cocoapods.org
using pre-processor macros you lose come compile time checking per target, test on separate targets • You can just deﬁne a constant set by the pre-processor macro • Keep it simple! Feature Toggling (Views) Two-Binary System
Builds are asynchronous so you can spend your time being productive while you wait • Saves time doing repetitive tasks • Makes the two binary system and feature toggling easier to manage • Teams can get passive notiﬁcations versus PMs asking for the status Automated Builds
schedule - i.e. Once a day, twice a day etc. • Try to be strict about your build regimen • Don't get overwhelmed by automation scripts, think of builds as a living document that will always change as your app requirements and team requirements change. Automated Builds
get daily builds • Don't need the testers physical device to install the app • Some allow feedback modules in-app • Some have crash reporting services • Isolate bugs on a per binary basis • Keeps track of dSYM and IPA ﬁles instead of checking it into source control App Distribution Why is it important?!