BROADCASTS.com

Jelly\u2019s done his homework, so the couch explores his solution to getting a scrollview to page with peeking content. They also weigh in on Watchkit, discussing the way it works and what the future implications might be.\n\nLike all the cool shows, this one starts with the intro, or at least it tries, as Jake leads everyone off track into discussion of podcasts (specifically Chat 10 Looks 3, Serial and Start Up), as well as their style and sound quality.\n\nFinally getting themselves into gear, Jelly starts the discussion with the results of the bet about getting a scrollview to \u201cpage\u201d with content that peeks on either side of the frame. Jake explains the problem he had, and then Jelly explains how he tackled the issue, as well as what he did with his results.\n\nMore follow-up about Swift brings discussion of a listener-submitted Swift style guide, and the oddities about the optional language syntax. This leads to Jake admitting that maybe he\u2019s still not clear about a few things, like how type inference works\u2026 or how arrays work, for that matter.\n\nJelly brings up the topic of Watchkit, which has been out for a few weeks now. Even though none of the three have actually done anything with the framework, they decide to weigh in with their first impressions. This inevitably becomes a discussion about the potential of WatchKit, and how the iPhone\u2019s ecosystem was moved forward by \u201cmisuse\u201d of API features.\n\nBen asks Jelly, as a hold-out on Storyboards, what he thinks about the fact that Watchkit apps are storyboard only. This, of course, leads Jake to get all excited and start explaining how he implemented IB_DESIGNABLE with a class and has fallen in love with it.\n\nTaking all of this back to Watchkit, Jelly points out that the \u201cstoryboards only\u201d approach \u2014 which he\u2019s totally cool with, by the way \u2014 might be suggestive of where Apple is trying to go with app development overall.