Naturally I wouldn't want to add a feature that made the iFly experience worse. On my middling performing tablet, it takes iFly only 15 seconds to boot. (And that's off the external memory card.) It doesn't boot faster on faster tablets?
In any event, since there's now a "Chart Expiration" page under Menu > About, that page shows that iFly already knows the expiration dates of charts without having to query the Data Base.
I had originally suggested that it query the Data Base every so often to check on chart expiration. But since that data is already known, I modify my wish to skip the Data Base check and to implement a different Warning scenario.
That, in addition to the Chart Expiration page, iFly pops up a window when any chart is equal to or greater than the tablet's (or iFly device's) current date. (I'm assuming that iFly devices are tablet like in that they keep an internal clock?)
The pop up window doesn't have to be specific. It could simply say "One or more of your charts has expired." (Like the GPS Warning pops up asking me if I want to enable GPS.) Or skip the window and if a chart has expired, simply take the user to the "Check for Updates" map to show the offending (red) state.
Since iFly already knows the expiration date of charts (presumably from when they're first downloaded) there doesn't appear to be a need to query the Data Base every time a User wants to check for updates. States could turn red on their own internally, whenever a chart has expired.
(I suppose this would mean a code change about how iFly thinks about the Data Base map. Perhaps the Data Base checking code could be repurposed into an internal check of the internal Data Base?)