Sponsored Link
No stress with last minute content changes
Contentful is the API-driven cloud CMS for mobile and web apps. Let marketing colleagues change content in your app without involving developers, or resubmitting the app. Contentful provides a powerful API and an easy to use iOS SDK and an Xcode plugin. We'll send an amazing Emoji mask to the first 100 signups. Just send "iosdevweekly" + your address to [email protected]
contentful.com
News
Introducing React Native
This is an interesting one. At this week's React JS conference, Facebook announced React Native which is a framework for writing iOS (and eventually Android) apps in JavaScript. We've heard this before right? Maybe not, details are a little thin on the ground at the moment but as I understand it there are no web views in sight on the device, everything is UIKit and they are also not pitching this as a write once, run everywhere solution. I'll reserve judgement until I've seen it but tweets like this from Andy Matuschak are a good sign.
Update: Elvis NuĂąez points out that there is already more information out about this, including code that I had missed.
youtube.com
Swift Development Courses on iTunes U
This probably won't come as a big surprise but this year's instalment of the Stanford iOS course is focusing on Swift rather than Objective-C. If you've been putting off getting started with writing iOS apps or learning Swift, this might be a good point to get stuck in.
apple.com
Tools
How To Use The 3 Instruments You Should Be Using
You are measuring your app's performance using Instruments right? If you aren't, or for anyone new to iOS development, David McGraw has a nice intro that covers three of the Instruments you should be using to measure performance and find problems in your apps.
xmcgraw.com
Code
Logging Excessive Main Thread Blocking
Justin Spahr-Summers was inspired by an internal tool used at Facebook called Watchdog, originally mentioned in this article, and implemented his own version. The tool logs whenever the main thread is blocked over a given threshold. Looks like a useful debugging tool.
github.com
Converting Complex Objective-C Macros to Swift Functions
I've always tended to stay away from writing complex macros in my Objective-C code but I do know they are popular among many developers. Luckily the transition of these macros to Swift is pretty straightforward and Andrew Bancroft has some examples, the resulting code is so much cleaner too.
andrewcbancroft.com
PrintlnMagic
Speaking of Objective-C macros, Arthur Ariel Sabintsev's project PrintlnMagic replicates the DLog macro in Swift. Once included in your project calling println() will also print the filename, function and line number. Looks very useful and could put a stop to println("here")... println("here2") while debugging. đ
medium.com
The curious case of rotation with multiple windows on iOS 8
I bet Peter Steinberger knows more about UIKit than any other developer outside of Apple. In this article he walks through a regression in iOS 8 related to window rotation and provides a pretty clean work around that works on iOS 7 and 8.
petersteinberger.com
Design
How Your Favorite Apps Will Look On The Apple Watch
Leandro Brasil imagines how several popular apps might take advantage of WatchKit. I think he's gone slightly overboard in some cases with how much functionality they will have but it's good to think about this stuff and the post might give you a bit of inspiration.
fastcodesign.com
The Making of Loose Leafâs Killer Feature
Fantastic post from the makers of Loose Leaf on how they really focused on the details of one specific tool in their app. You can tell even just from the GIFs here that it works great and was worth the effort.
getlooseleaf.com
Videos
Books
iOS 8 Day by Day
Sam Davies has put a book together from his excellent iOS 8 Day by Day articles. There's so much being written about Swift right now that these posts (and the book!) are a refreshing look at developing for iOS 8 (even though the code samples are in Swift, the posts concentrate on iOS rather than the language) and I'm very pleased to see them collected into a book.
leanpub.com
Sponsored Jobs
Mobile Developer at The New York Times
Build innovative apps that make a difference and are used by millions.
nytimes.com
iOS Engineer at Scribd, San Francisco
Make reading easier and more beautiful on mobile devices!
thesourcery.com
Senior iOS Engineer⨠at farmerswife, Mallorca (Spain)
Help create the next generation of project management tools.
farmerswife.com
This week had both good and bad news. In good news, iOS 8.1.3 now requires less space to upgrade. On the other hand, the bad news is that logging into iTunes connect now gives you access to a random account đ.
All joking aside, I think there is a serious point to make here. From what I can determine from the tweets, there was about a 30-45 minute period when people logging in to iTunes Connect were seeing other random accounts instead of their own. After that, iTunes Connect was shut down for about 4 hours before silently coming back up as if nothing had happened, while the most useless page on the internet stayed all green for the vast majority of the downtime.
There was naturally lots of speculation on exactly what the issue was. I think the most likely is something I saw Padraig Kennedy speculate on, that what people were seeing was a staging/test system (maybe for Analytics?). However, even if the data was not editable it does appear to be real data, with real unreleased apps/app versions and real revenue (we're seeing revenue information for another developer's apps in AppFigures - This is incorrect, revenue was not appearing in AppFigures. See my update below for an explanation). Whichever way you look at it, this was a serious bug/issue.
Now I'm being quite harsh here. I understand that these mistakes occasionally happen, and when you're the size of Apple those mistakes become very public. There's nothing that can be done about the fact that this occurred. What I have a problem with is the way it was handled. I know Apple don't make public statements about this kind of event until they are certain what happened. But to bring the service back up without any kind of statement is simply not good enough. For it to be brought back online, you have to think that Apple were 100% certain that the issue was solved. Why are we sitting here more than 18 hours later with no idea what really happened to our data?
Update: I've been in contact with AppFigures and it does seem that revenue was not leaked into AppFigures. We had another iTunes Connect account that had been added to the AppFigures account and we had not noticed these apps before (it's on a big AppFigures account and we were checking for strange data this morning specifically after last night's events). My apologies for not investigating this part of the above thoroughly enough before writing about it. Dave
Dave Verwer