Maybe this was accidentally released too early (unlikely), or maybe it was released and a bug was subsequently found (more likely). Either way, we got what ended up being a sneak preview of the new Radar interface this week. It looks to be a vast improvement in terms of UI but no fundamental changes such as options to make reports public. Still, it’s definitely a step in the right direction.
Adam Swinden has created a Google spreadsheet to help people connect at WWDC this year. There are over 400 people already registered with this list but that’s far from the thousands that are going to be attending WWDC. So, if you are not already on this then you probably want to add yourself and sign up for the Glassboard invitation as well.
As always, there are many WWDC first timer guides which have been published or updated over the last couple of weeks so it’s hard to pick one. I ended up picking this comprehensive guide from Uli Kusterer this year so if this is your first year then make sure to read this so that you get the best out of (or just survive) the week.
Hopefully you are already signed up for a few of these as many of them are sold out. You shouldn’t struggle to fill every night (and lunch, and breakfast) with an event of some sort if you want to.
I wished for something like this when I mentioned ImageOptim previously, a tool to run through different PNG and JPG optimisation techniques and export an optimal set of assets. Sure enough, Oliver Michalak has put together an app which automates the process of analysing all image resources in an app and providing a quick and easy way to get the best optimisations out. I ran it against one of our image heavy apps and it had remarkable results with almost no change in the visual quality of the app.
Beta version of a new view hierarchy visualisation app in the same vein as Spark Inspector which was mentioned back in May. Whether you choose this or Spark Inspector, it’s certainly nice to have a more visual way to debug or tweak a view hierarchy. I need to check both of them out properly so I won’t indicate any kind of preference between the two here just yet.
Carl Veazey with an article on preempting the Apple rejection caused by using private or disallowed selectors like uniqueIdentifier. It’s easy to check your own code for this but harder to check third party libraries, especially if you don’t have source. Learn how to use otool to track down the offending library so you are able to upgrade/replace it and get through review.
Joris Kluivers with an interesting experiment looking at whether it is possible to bring the ability to render Quartz Composer compositions under iOS. He has a largely working version, although he advises that this is still very much a work in progress. Like Joris, I don’t see this as a way to build iOS apps but might work out great for an occasional transition and especially for prototyping.
We sometimes take for granted the presence of an “always on” internet connection on our iOS devices but the number of app rejections I hear about which still find issues with apps running offline means we still have a way to go. This talk by Ken Auer goes through some common scenarios and has plenty of tips on how to cope gracefully with intermittent connectivity.
Anthony Tseng on why users work better with rounded corners rather than sharp edges in user interfaces. The basic theory is that we are conditioned to avoid sharp edges in real life and also that we can follow rounded lines easier than we can hard corners but have a read of the whole thing to get the full details.
The first two (or so) lines of your App Store description are the most important but how much text is actually being displayed? It’s not even the same amount on the iPad App Store as it is on the iPhone. Find out what will actually be visible on each of the App Stores with this simple tool from Marc Edwards.
If you can’t make the WWDC keynote in person, maybe amuse yourself with a game of bingo while watching along?