This might be more of a thing with mid-to-larger organizations, but we have a subset of users who will lock a computer instead of closing out of applications/databases in Notes or rebooting their PC until forced by a monthly patch Tuesday. This is a problem for actively maintained applications that receive regular design updates and the user session being days/weeks old and running on the prior design which may have defects. As such, they keep alive bug(s) that have been fixed and create support headaches as a result.
I understand this would not quite work for local replicas (though offline users are better at syncing up in general), but for Online users it seems that there should be some possibility to ensure they are dealing the latest design. If it cannot be automatic, maybe the client could poll the design and flash an indicator that they have an out of date session/version of an application/database based on a hash of the design elements. Maybe just a red circle notification on the client tab for the app like in iOS to give them a nudge or a pop-up if the underlying design has changed and their session is over 24-48 hours old.
