- An Indie’s Guide To the Press
- Great Watch Apps are Great Complications
- When Your Code Breaks the Compiler
- Writing Custom Animations on iOS
- Kill Your Giant viewDidLoad
- Improving Code Quality
- Using swiftenv To Install and Manage Swift Versions
- Contributing to Open Source Swift
- Protocol Oriented Programming
- Introduction to Protocol-Oriented MVVM
- Debugging – A Principled Approach
I’d been really looking forward to the Apple Event yesterday with the hopes of some major updates to the MacBook lineup as well as a hope of some updates to the Apple Watch hardware – both of which are, in my opinion, overdue for updates. The bad news is that I was disappointed – on both fronts.
The MacBooks weren’t mentioned at all and there was little news on the Apple Watch front apart from a price drop and the addition of some new bands. The price drop is definitely welcome but I suspect many will delay purchase whilst they wait for second generation hardware to appear.
There were some highlights from the event. Generally they can be summed up as ‘Similar specs. Smaller sizes. Lower price points’.
First, as much of the media were predicting, it seems that at the rumours of a new 4 inch iPhone were true. With the announcement of the iPhone SE , Apple announced a new device with almost the same hardware as the iPhone 6S but with a smaller screen. I suspect it won’t be long before we see this new device as the de-facto entry level iPhone.
On the iPad front, the announcement of a smaller 9.7″ iPad Pro followed a similar vein. From watching the keynote, the screen technology seems to be the big selling point here, with a less reflective screen and “True Tone” technology built in that adapts the screen color temperature to match the devices ambient lighting conditions. The Apple Pencil will also be supported, making it a slightly more mobile solution than it’s brethren. Personally though, I’m still drawn to the larger-sized screen of it’s 12.9 inch brother so I’m not sure I’ll be changing my ongoing campaign to get my wife to let me buy one!
From a development point of view, the most interesting announcement was CareKit . Sharing similarities with the ResearchKit, CareKit will also be open sourced and promises additional functionality to help users keep track of their medical treatments and share information with their doctors. It’ll be interesting to see what the framework itself contains as well as seeing what we can do with it. I’m definitely thinking about ResearchKit and CareKit as topics for future articles.
Overall then, my general impression of yesterdays event was that it was a bit of a holding-event. There were obviously announcements of new hardware devices which are welcome, but none of them were particularly groundbreaking. The expanding hardware line will likely result in an influx of new users to the iOS platform which can only be a good thing and CareKit is definitely interesting but I’m still hoping for some more ground-breaking announcements as we head into WWDC.
@conradstoll on why designing great complications for the Apple Watch is hard.
The development tools we are provided are extremely powerful but there are still times when we see some strange behaviour that we don’t fully understand. In this article, @ManzoPower reminds us that with Swift being open-source, we now have the option of digging into the compiler source code for ourselves.
In this article, @nickoneill looks at how we can use closures and property initialization to organise and simplify viewDidLoad methods. A nice idea.
If you’ve been messing around with the different Swift snapshot builds on Linux you’re going to love this tool. Inspired by RVM, the Ruby Version Manager, swiftenv from @kylefuller provides a powerful way to manage your different swift installations. This article from @benatbensnider provides a great introduction.
A powerful caching library from the team at @SpotifyEng that supports caching of NSData objects with specific TTLs along with additional options to control how that data is stored on disk.
From @Swift_Studies is a simple Swift package for measuring and reporting the time it takes to perform operations. Useful for optimising your code.
BWWalkthrough is a custom framework that simplifies the creation of custom walkthroughs for your iOS app. In this article, the author of that framework @bitwaker shows us just how easy it is to get up and running.
In this video, @jesse_squires talks about the various Swift open source projects, the LLVM compiler and talks about how and why you should get involved.
Protocol oriented programming and the three princesses. @greg3z with a short and amusing introduction to protocol oriented programming.
Having had your introduction above, we also have this video from @natashatherobot provides a great introduction how, through the use of protocols, you can hugely simplify your table view cell configuration methods. Worth watching.