Paper logbooks have a certain dignity. They also have a gift for disappearing into the flight bag precisely when somebody important asks to see them.
Going digital introduced new possibilities for inconvenience. I tried interfaces, exports and workflows that made handwriting look positively futuristic.
FLYLOG.io was a welcome change.
Clear enough to be useful
I liked the browser experience on my Mac: readable entries, accessible totals and less unnecessary menu archaeology. The phone experience felt consistent with it.
My migration went well. Entries arrived and totals made sense. Even so, I would always keep the original records and check both individual flights and sums. A tidy interface cannot certify that the data beneath it is correct.
Help, not absolution
Calculations and checks can reduce work. They do not remove my responsibility for the logbook, nor guarantee that every export meets every authority's requirements in every situation.
For current features and plans, see FLYLOG.io. This is my experience, not a permanent specification sheet.
The strongest compliment I can offer is a practical one: I spent less time thinking about the software.
Exactly as it should be. The flying is meant to be the interesting part.
Personal aviation writing, not a flight briefing. Use current official information and the applicable aircraft flight manual.