Writing automated acceptance tests of iOS apps has always been tricky. Prior to the introduction of Apple's UIAutomation framework, there was no official way of writing automated UI-driven tests for iOS. There have been numerous third-party attempts at coming up with an automated testing solution over the years - some bad, some good - and I think I've probably tried most of them.
I'm not a big fan of singletons, especially when they are used as they often are - as glorified globals. That being said, it occasionally makes sense to have some kind of shared instance of an object; not a true singleton that strictly prevents more than one allocation, but a convenient default instance.
Reading Marcus Zarra's own style guide, I thought I'd write a post outlining my own conventions.
Today marks the beginning of the Apple WWDC 2011. I'm not normally one for attempting predictions, especially not on my blog, so this won't be another predictions post. If you want one of those, then Gruber is your man.
Twitter for iPhone (formerly Tweetie) has long been one of my favourite iOS Twitter clients (#dickbar fiasco not withstanding) and has some innovative UI features, particularly it's much imitated "pull-to-refresh" behaviour.