Happy new year! The holidays are over and I’m back to work, having made no progress really since the last post. Except that I had time to work on some ideas for how to make accessing the data faster – long drives and lazy afternoons are good for that kind of thing.
I also have a pretty clear idea for what kind of functionality I want the very first release to have. I want four screens:
- Saved stops/routes that also shows a list of the nearest stops
- A list of stops that you can search by name
- When you click a stop you get the departures from that stop (*)
- When you click a departure you’re shown the entire trip (*)
And finally, on the screens marked with (*) there should be an option to “save” or “pin” that puts an entry for that stop/route on the saved list. That’s it. It’s not everything you want but it’s enough to be useful. It’s somewhere to start.
Oh, and I’ve bought a used iPhone 5S for developing the iOS version, it should be arriving by mail within a few days. I was waiting until after Christmas so I could by it on sale. Once I’m done with the initial android version, or in parallel, I should spend some time on the iOS version as well. The problem with iOS is that I’m an android user myself so I don’t have a good understanding of how apps should work on iOS. So even though the iPhone is for work I want to use it as my own phone as well, at least some of the time, so that I can learn how iPhone apps work.
Should I give releases names? I probably should. In keeping with the working title of the whole project, pensive agouti, I’ll name them after things agouti eat. They eat a lot of different things so that should give me something to pick from. I’ll call the first release apple because, ironically, it’ll probably be android-only. Here are some more names, now that I have the list of agouti foods open,
- apple
- yam
- broccoli
- banana
- carrot
That should cover me for a couple of months.
