What's changed in v2.0.0
This release is a significant update focused on cloud sync reliability, performance, and a cleaner user experience. The JDBC-based cloud layer has been replaced entirely with Supabase Edge Functions, sync is now batch-based and runs on a dedicated background thread, and several UX improvements round out the release.
☁️ Cloud & Sync
-
Supabase Edge Functions replace standard JDBC — Cloud communication now goes through Supabase Edge Functions instead of direct JDBC connections. This removes the need to expose raw database credentials and makes cross-environment deployments more secure and straightforward.
-
Batch cloud sync instead of per-record uploads — Unsynced local records are now pushed to the cloud in a single batched request rather than one API call per record. This significantly reduces network overhead when multiple sessions have accumulated offline.
-
Cloud sync runs on a dedicated background thread — Sync operations are dispatched to a separate thread, keeping the main application fully responsive during network calls. The UI no longer blocks while records are being pushed to the cloud.
⚙️ Configuration
- Manual configuration sync button — Configuration is no longer fetched from Supabase on every run. A dedicated Sync button lets administrators trigger a config refresh on demand, eliminating unnecessary network calls at startup.
🖥️ UI & Performance
-
Sorted combobox entries — Dropdown items are now displayed in sorted order for easier navigation.
-
General efficiency improvements — Internal refactors across the codebase improve startup time, reduce redundant operations, and clean up legacy patterns from v1.
📦 Installation
Extract SessionTracker-Installer-v2.0.0.zip, update Installer/gui/config.properties with your database details, then compile the .iss script using Inno Setup to generate your installer. See the README for the full setup guide.