This post explores what’s next for my Fort Collins for Kids app. So far I’ve not only been building this thing as I go, but I’ve been imagining it as I go. Iterative design and coding is one thing, iterative requirements are another. I’ve decided I need a better idea of what the final app will look like. If you read my previous entry, you know that I’ve decided that this will be an iPhone-only app.
Who are the target users?
It’s always essential to consider the users for your app. In my case, it’s parents and grandparents who want to find something to do with their kids. Some things they will want to consider:
- Is the activity inside or outside?
- What season is it?
- How much does it cost?
- What ages are appropriate?
- How do you get there? (Ah! A map!)
- What does it look like? (Ah! Photos!)
- Where is parking?
I’m sure I’ll come up with more as I continue thinking about this.
Goals for Iteration 3
This leads me to the goals of the next phase of the app development. Here they are:
- Define functionality of the Fort Collins for Kids app, including what kinds of searching will be allowed.
- Define data model required to support the functionality- including “domains”
- Identify any special classes that will need to be created to support domains.
- Get provisioning and certificates working on all of our new devices.
- Build a plan for Iteration 4, which will be the next piece of the editor app, and Iteration 5, which will start development of the main application.
Time to start working!