I saw the list of the top 5000 CocoaPods by download count, shared by Orta. What got my attention was that more than half of the top 35 pods listed are owned by big companies (Google, Facebook). And as Nick Lockwood observed on Twitter, some of those pods aren’t even really open source, being only a Swift wrapper over a precompiled framework. Now don’t get me wrong, those are solid, stable tools that get the job done, and I’ve also used and still use some of them in the projects I work on. I just wanted to reiterate on something that I also wrote about in a previous issue: we as developers need to be aware of all the implications of adding other SDKs to our app. The SDKs included in an app get access to the same data as the app (which can include keychain data, photos, location, camera, logins and others).
On a lighter note, you’ll notice that I’ve added a 🙃 next to one of the tools included in this edition. That’s because although I doubt anyone will find it useful in a real world app, I had too much fun when I saw it not to include it in this week’s nesletter 😄.
- Response: The Laws Of Core Data, by @mzarra
- How StackView help your iOS app to be more dynamic, by @pmusolino
- Natural Language Processing on iOS with Turi Create, by @TheMikeKatz
- Running Xcode Playgrounds on Travis CI, by @mattt
- Design Patterns in Swift: State Pattern, by @dagostin
- Guide to Codable Sample Code – Xcode Playground Sample Code for the Flight School Guide to Codable, by @mattt
- Sample Code of the App Architecture Book, by @objcio
- ClassicKit – A collection of classic-style UI components for iOS, by @blaketsuzaki – 🙃
- 11 principles that help me write better code, by Belle B. Cooper
- After 5 years and $3M, here’s everything we’ve learned from building Ghost, by @johnonolan and @erisds
- How to Run More Inclusive Meetings, by @katieburkie
- Privacy: A Quick Overview for App Designers, by @brianpagan
- Animation in UI Design: From Concept to Reality, by @tubikstudio