Coming back to New York after a couple months away, I’d accumulated quite a few odds-n’-ends that needed attending to. In the meantime, I was anxious to get back to work, and so I took a brief detour and joined the ranks of indie developers who, unwilling to accept the multitudes of existing well-executed Twitter clients, decided to build my own. But mine’s a little different. I’ve dubbed it a “novelty” Twitter client, which really only stands to discourage consumption by those who assume it might actually be a traditional (read: fully capable) client. Takeaway Tweets allures not by it’s array of features as compared to existing clients, but rather by it’s lack there-of.
And so I bring you Takeaway Tweets. Half mystic, half Twitter client, it is, at the very least, unlike any Twitter client you may have used. Takeaway Tweets begins by scouring Twitter for tweets marked with the hashtags #TakeAwayTweets or #FortuneTweets. What it finds, it wraps in fortune-cookies and presents to users of the app for consumption. The premise, then, is essentially crowd-sourced fortune tweets. Mixed with a little sauce to favor user-tagged fortune tweets over the fortunes of the anonymous masses, extended to support wrapping a user’s entire timeline in fortune cookies (well, up to eight entries), it actually progressed into something that, once-or-twice a day, can be quite fun to use. I’ve yet to find any other Twitter client that suggests the act of consuming of a single tweet be any more crunchily-satisfying.
Half the fun, of course, is reading and sending wisdom-filled tweets to friends, so naturally the app supports traditional Twitter functions such as compose, reply, retweet, and quote.
Given a relatively modest scope and feature set, Takeaway Tweets moved quickly through design and production, but it did give me the chance to dabble in a few areas of the SDK that I’ve been meaning to dabble in since last year’s WWDC: This represents my first Automatic Reference Counting project (incidentally, also the first project I did what my first Obj-C teacher told me I never would: Found a leak in an Apple framework), it was also my first foray into Storyboards (really, really fast if you can work within the confines). This is also the first app where I developed all the art and audio components completely independently.
It’s on the app store, and it’s guaranteed to entertain you for at least 3-5 minutes while you try and figure out how to use it.
Grab a copy!