jwt1356

I actually just packed a SmartLPV 160 into an Icon I4 last night (in New England), and that was tight. Given I'm not as used to the bulk distribution in a Smart compared to PDR or OP, but a 175 would have had me cursing up and down the loft. I've also done tight reserve/tight main combos on Vectors, would not recommend.

Fair enough. I've seen enough bad UI choices in the mobile world that this made something itch between my ears is all, but it sounds like you've got a plan. Real world convenience is going to depend on the platform too, I suppose i.e. touchscreen vs mouse and keyboard. The Android app "Skydiving Logbook" has a decent solution with a pre-populated list of aircraft, DZs, jump types, etc. that a user is free to redefine or add to. It's either clunky or convenient, depending on the person, but could be one approach. I just recently did something similar--but less intelligent on the data entry side--in a script for Google Spreadsheets (and Google Forms), so it'll be interesting to see where yours goes. Automatic email/calendar reminders for the customer are nice if you can figure out a good system for that.

Not really answering your question, but the worst thing you can do for production software is impose unnecessary limitations or an obtuse UI. Why do you feel the gear needs to be enumerated rather than simply being a text input? If you're dead set on using a list, just add the popular makes/models but also add an "other" option with a text box so that users can input whatever is required. You'll never predict every use case, and a single hole in a log book makes the entire thing useless.