For example have the logs row highlighted red or orange if the signature is missing or has become invalidated.
This would make finding such errors much easier at a glance.
Hey Josh, thanks for this additional suggestion.
Smart Logbook should already warn you if you try to save a flight after making a change that invalidates an existing signature. That’s designed to make it harder to inadvertently make such a change. Let me know if you don’t see that behavior. It’s supported in both the iOS and Android versions of the app.
For highlighting log entries without a signature, this one is a bit trickier, because the app needs to know when it should have one. It could flag any entry that’s added with Dual Received time but no signature, but sometimes you may want to add logs like that (e.g. when adding or importing entries from a paper logbook). An alternative might be to expand the flight filter functionality to be able to find flights without a signature. Then you could periodically do audit your logbook yourself to find entries that should have a signature, for example, by setting the filter to match flights that both 1) have Dual Received time, but 2) do not have a signature.
Those are some good alternatives. Adding a minu signature icon on the tabs could work too.either as a grey icon to show it was signed or no icon to signifying no signature.
I like that idea, too! I’m actually planning to provide more customization options for rendering flights in the list, so I’ll try to include the “signed” status in the list of options.