How to build a tidy customer-facing iOS library / framework

It’s coming to the end of a project and the deliverable is a library for iOS. A lot of devs/agencies are happy to distribute a .zip with the prebuilt .a, separate .h files and resources, but there is a cleaner, more customer friendly way: We package everything into a .framework & .bundle then distribute these as a .dmg.

We then move from giving customers a .zip with lots of different components that they have to import into their Xcode project, to a single .framework and .bundle that they can just drop right in and use, this also makes it easier for customers in-future should they want to move to an updated version of the library.

Hit ‘Read more’ to find out how

Read More