Quote:
Originally Posted by lenchan
That would put a reasonable scope for the app. But still, even for the front-end, it will take some effort/care to produce a user-friendly interface.
So, what are your requirements for a Balloon Pilot Logbook? Did anyone actually contact you?
|
I would tend to agree...the user interface is most important.
No has yet contacted me - so, let's go with the very simple and consider the following fields:
Date - (MM/DD/YYYY)
Time - For Balloons, it's AM or PM. Actual time doesn't matter.
Balloon Information
- Make
- Model
- Balloon N#
Flight Information
- Launch Site (if done right, this could pull current GPS location)
- Landing Site (if done right, this could pull current GPS location)
- Distance
- Max. Altitude
- # Passengers
- # Landings
Wind Data (all drop downs selections in increments of 1 or 2 knots)
- Speed at Take Off
- Gusts
- Speed at Landing
Remarks, Procedures, Maneuvers - Free text field
Piloting Type Time - each with numerical entry (XX.xx Hours)
- Free Flight
- Tether Flight
- Instruction Provided
- Instruction Received
We could go one step further and allow the balloon type be configurable in that the user preconfigures the Balloon Information section, provide it a name (balloons are all named) and then make it selectable in a drop down or what ever is easiest as opposed of having to enter the information each time.
Even easier than this would be a Balloon Crew Log with the following information:
Date/Time (AM/PM)
Company
Balloon
Pilot
Launch Site
Land Site
Comments
Paid Y/N?
Let me know if you have any questions...