This blog was co-authored by Yulia Tolskaya. The full source can be found here.
In our last post, we covered the steps to bootstrap a Cedar-tested iPhone app. In this post, we’ll add some basic features (like buttons!) to the app.
The feature we want to start today is the ability to create and save a named scoresheet. We’re thinking a button on the main page with a list of saved scoresheets. Tapping the button would take us to a page where we can type in a name. Since we have Cedar, we’re going to TDD the whole thing. Hopefully this post and the next post will help teach the basics of navigation and models in relation to unit tests in iOS/Cedar. So, let’s get started!
The app we’ll be building in this blog is a simple score keeping app. The requirements are simple: I want to be able to track my weekly Sheepshead game scores by opening up my ScoreKeeper app and writing out each player and their score for the day. I also want a running average of score per scoresheet to prove that I’m actually a decent player, I just keep losing over lunch.
The problem is, I don’t know any iOS. I searched our own blog stack and the intertubes of blogs and found compendiums of misdirection or guides assuming I already knew iOS. I know nothing. Quite literally, the square brackets scare the hell out of me. So I’m going to do what any good pivot would do when scared shitless: I’m gonna blog it. This will be a step-by-step of how to bootstrap, implement, and improve a “simple” iOS app.