Leap offline mode is absolutely unuseable for us. Any need to reboot a machine or otherwise clear a cache result in loss of ALL the collected data. Many of our users try these as troubleshooting steps for various problems before calling us. Using Leap Offline is putting our staff in a situation that impacts them negatively for taking steps that would otherwise be the right thing to do. They are not tech people. They do not understand what may reset a cache and what might not nor do they understand how a web app makes use of the cache they just cleared to store all the data they've created up to that point while in offline mode. We actually have to install the client on every desk PC just to handle offline mode. If the client stops working because it isn't being maintained this will create an issue for us big enough to make us consider switching away from Polaris to something more reliable. There needs to be a better solution for offline mode even if it is a dedicated utility application.

Please, please find a solution for this. It just seems with such sophisticated and expensive software, you wouldn't need to rely on browser cache for offline transactions.

Yes, please!

As mentioned by others, we have libraries who use Leap for circulation, but revert to the offline client because of the fear of loosing data.

I agree with the comments above. Leap offline is not a reliable solution for our library. We need a better way to work offline without risking our transactions.

Due to the risk of data loss, we cannot consider Leap offline a viable option at this time. Not relying on saved data in the browser cache would be a significant improvement.

We are a cooperative library system and have 14 member libraries, each with their own IT support and each with their own desktop security and browser settings. (Which we aren't able to control.) The concern about working offline in leap and losing data if the cache is cleared has been a hurdle to libraries adopting Leap at the circ desk.

We use Leap exclusively for front-line work EXCEPT we still use the offline version of the Polaris client for this very reason. We struggle whenever we go offline because our staff is no longer familiar with the client at all. It's as though they are being asked to use two completely unrelated systems that just happen to access the same databases. It would be great if Leap Offline could be modified to reduce the risk of losing transactions.

Saving the information in the browser cache could lead to catastrophic data loss. This renders the offline capabilities of Leap as unusable in many organizations.