Welcome to Issue 150 of Swift Developments! So with Swift Development reaching another half-century (woot! 🎉), we’ve not got long to wait now before this years goodies from Apple. From my perspective I suspect that most of the interest is going to be around the next generation of iPhones, but with the early leaks I’ve seen, I find myself more interested in the next iteration of the Apple Watch. If everything turns out as reported, I suspect my wallet is going feel a little lighter in the near future. Have a great week and enjoy tomorrow’s event if you’re planning on watching!
Business@cocoawithlove on the history, lessons, and his reasoning for finally retiring, his app StreamToMe. Props to Matt for sharing this one.cocoawithlove.com@amirrajan with the manuscript of his book – Surviving the App Store. Published under creative commons, it has a bunch of great tips and interviews with other indie game developers discussing what it takes to make it as an indie game developer. github.com@appinchina highlight some of the key factors to consider. medium.com
Design@101babich look at some of the strengths and weaknesses of this ‘back-to-basics’ approach along with some practical tips and recommendations.uxplanet.orgraywenderlich.com
Swift@johnsundell illustrates in this article, through the use of the the
guardstatement, the Swift language tends to promote the former approach which can have some serious benefits for code clarity. swiftbysundell.com@SteveBarnegren has been looking at the differnences between these two patterns and trying to identify some specific recommendations of when each approach should be used. itnext.io