Welcome to this weeks issue of Swift Developments! Before we get to the links this week, I just wanted to mention that there isn’t going to be an issue next week. With all the announcements that will undoubtedly occur next week, I’m sure you will already have more than enough reading in your inbox anyway! With any luck, by the week after, I’ll have had a chance to dig into everything and bring you the best of the comments, links and articles from around the community. In the meantime, have a great week and enjoy everything WWDC has to offer – whether you’re there in person or not. 😎
I always find usability case studies interesting as there usually a whole host of lessons that I can extract and apply to my own app designs. This article from Sally Chen Zhen is no exception with a detailed dive into the useability aspects of Apple’s existing News app and a work-up of an alternative.
The concept of ‘self-documenting code’ can often be a contentious amongst developers. Regardless of your stance on the topic – you’ll probably agree that striving to write your code in a way that is as easy as possible to understand is a laudible goal. @johnsundell provides some tips that will help.
Wanting to optimize your app? Lazy initialization may be one option to think about – an option that’s particularly useful for cases where initial values are expensive to create. @kharrison provides a quick rundown of all the nuts and bolts.
@aligatr tackles MVC syndrome with this new article on how to refactor your
UITableViewController code to move the
UITableViewDelegate into a separated dedicated object.
Playgrounds can be a great tool for rapidly iterating on new designs. Putting Xcode issues aside, @alexisgallagher shares some notes and observations on how to get the best experience when prototyping custom views using Playgrounds.
Although it’s nice to be able to develop something unique every time we build an app, in some cases, this just isn’t possible. Sometimes there is a need to develop different variants of an app for different clients. So if we are faced with this situation, what can we do to maximize our code reuse? @myrenkar shares some tips.