….And we’re back! It’s been nice to have some time off over the Easter period and I even got some time to work on one of my side projects which has been great (hopefully more details on that in the coming months). In the meantime though, there have been some great articles popping up around the community and this week is no exception including quite a few around Swift itself. Enjoy.
Designing an app that draws your user in and invokes an emotional response is no mean feat at the best of times, but what if your app doesn’t exactly lend itself to invoking enthusiasm and excitement? Alice Kotlyarenko provides some tips on how to design emotion into your own app along with a number of examples of apps that have got it just right.
Swift 4.1 has been out in the wild for a couple of weeks now but beyond the attention grabbing features, @slava_pestov highlighted some less visible improvements that are worth knowing about and in some cases, lay the groundwork for the future of Swift.
Things are moving fast in the world of Swift. With Swift 4.2 now only days away from it’s final merge from the master branch @twostraws provides a roundup of some of the improvements we can expect in the next release.
With Swift heading towards it’s 4th birthday (well at least the public one), @terhechte looks at Swift’s position within the wider software community and takes a look at whether Swift is really ready for main-stream adoption beyond the Apple community.
With subscriptions, still a relatively new concept for many app developers and Apple continuing to finess their subscription rules, @iKenndac provides some useful guidance for those wishing to avoid repeated app review rejection and successfully navigate the legalese surrounding subscription-based pricing.
I came across this article whilst I was off. It’s a nice tutorial from @MDevSA on how to use the power of Swift protocols to write your own networking layer without any third-party dependencies. Good stuff.
Auto Layout can provide a powerful way for your app to adapt it’s content to changing screen sizes and resolutions but it’s not always used to it’s full potential. In this article, emiliopelaez looks at some of the more advanced auto layout techniques which help reduce code in your view controllers and let your app easily adapt to changing content sizes.
Guilty of this? I have to admit, I am on occasion but @cocoafrog has some good points on why you should take a moment to think about how you are naming your action methods.
Build it, Test it, Deliver it! – Complete iOS Guide on Continuous Delivery with fastlane and Jenkins
@KoromikoNeo shows you how to setup your own multi-environment continuous delivery pipeline using a combination of Jenkins and fastlane and provides some useful tips on navigating the code signing issues that can sometimes occur.
In this try! Swift Tokyo 2018 talk, @samuelgoodwin dives into the Responder Chain, looking at how your key press, screen tap or mouse click works it’s way up the responder chain to reach the it’s corresonding handling code and how you can break into that chain with your own code to provide your customer even handling.