Ok, so what do I want from an iPhone App? How about I list the requirements as I see them, and order them from highest to lowest? I have an idea that I can then choose a bunch at the top of the list and say “this will be the first release”, then a bunch below that to say “this will be the next release”, and so on down the list.
The perfect iPhone logbook app:
- Must not require an internet connection!
- User must be able to enter a new flight.
- User must be able to browse existing flights.
- User must be able to total up existing flights
- A flight consists of a brief description, a series of one or more locations, the aircraft that was taken, and the number of hours spent in certain activities such as “Pilot in Command”, “Cross Country”, “Dual Instruction” as well as counts of other non-timed activities like “Day Landings” or “Precision Approaches”.
- A particular aircraft should be known by its capabilities so that the user can get totals of time spent in those capabilities, such as single engine or multi engine, land plane or sea plane, complex, high performance, turbo prop, jet, etc.
- User should be able to filter on date ranges, capabilities, aircraft flown, activities logged, etc, in both the browse and total functions, so, for example, you can total up how many flights you took where you made a night landing in a complex aircraft while pilot in command, or see all the flights where you landed in Syracuse (KSYR).
- User should be given warnings of “currency” items, based either on recently logged flights, like if you’ve gone 90 days without 3 day or night landings, of for calendar items like when your medical expires.
- User could track other things in the flight, such as who else flew with you or flight number that would be filter-able
- User could have an unstructured note field to note down other facts about the flight that are not filter-able.
- User could export the flight log to a Google Docs spreadsheet. (Some other iPhone apps do this – I wonder if there is an API?) (Obviously an internet connection would be required during this operation)
- User could import the flight log from a Google Docs spreadsheet. (I have no idea if that’s even possible!)
- User could customize the duration and count fields for flights.
- User could customize the rules for currency, even combining several factors.
- Application could publish an interface so that other apps (like CoPilot, for example), could transfer information from a flight that was planned or flown into the logbook.
That should keep me busy for a while, eh? Any additions?