The main point in all these discussions is that although these libraries and dependency managers allow you to quickly and easily add functionality to your projects they can also bite you. The issue is one of control. If you do not have direct control over everything that is needed to build and release your project (and instead pull those dependencies down at build time), you are at significant risk of those dependencies either disappearing (as in the Node case) or at least changing under your feet (as is the case if you don’t specifically state the versions of those third-party dependencies).
The lesson then, is to make sure that you have everything you need to build your projects fully controlled in a version control repository that you own. That means the code, the libraries, the tools you use to build them and any other resources that you may use. That way, if things do disappear or change unexpectedly, you are fully insulated from those changes, you can still build your projects, and you can then make conscious decisions about if, and when, you are going to upgrade. This week has been a warning shot across the bows for many and one that is worth paying attention to.
10 Styles of App Store ScreenshotsApp screenshots are a key part of the marketing for your app within the App Store. In this article @dancounsell provides a good overview of the different styles and options that you might want to choose. dancounsell.com
@GergelyOrosz recounts how he, and the team at Skyscanner, have been gradually transitioning from Objective-C to Swift. It provides some good tips for teams that might be facing the same journey. codevoyagers.com
Design@robjama digs into this problem, dissecting some of Apples design and App Store recommendations to try and identify just what goes into making a successful app. medium.com
Swift@AndyyHope make things a whole lot cleaner and with the additional selector safety introduced in Swift 2.2 I’m pretty sure I’ll be adopting them in my own code going forwards. medium.com
@cocoawithlove takes a deep dive into the concept and nature of errors, looking at what errors actually are and looking at some of the complications that surround them. cocoawithlove.com
Libraries and Frameworks@sandofsky in which he talks about due diligence and the decision making process you should be going through when deciding whether or not to use a third-party library within your app. It’s worth a read. sandofsky.com
@biz84 aims to help with this by providing a lightweight, pure Swift API that supports product retrieval, the product purchase process, restoration of previous purchases as well as receipt validation. github.com
Videos@bobbins talks about the 7 Principles of Design. Taken from the book The Design of Everyday Things by Don Norman she shows how these very same design principles can be applied to the app design process to enhance (amongst other things) with discoverability of your apps and the feedback that your users get when using them. realm.io
@jeffhui talks about all the things that you need to think about when creating a library of your own including APIs, testing, continuous integration and package management. As part of the talk he walks through a complete example which definitely helps with the understanding. realm.io