v2.3.0

ThreadsVault Desktop v2.3.0

Added

• Layered import workflow with destination selection before file selection.
• New import targets:
  • PC database
  • Android database
• Dashboard database switcher to toggle between PC and Android. to the backups imports .JSON files from ThreadsVault, Android version and the first one of both (I'm aware of the Android version needs some improvements like a good polish in UI , this is in my ToDo-list, but this is massive because too many projects and brainstormings)
• Active database indicator in the dashboard.

Changed

• Import flow is now target-first:
  1. Open import
  2. Choose target database
  3. Select backup file
  4. Import into selected space
• Storage architecture now supports dual data spaces with isolated persistence.

Fixed

• Prevented accidental overwrite of the daily PC vault when importing Android backups.
• Tauri packaging issue when bundle.resources expected bin/* but no files existed.

Technical Notes

• Desktop (SQLite):
  • PC -> threadsvault.db
  • Android -> threadsvault-android.db
• Browser (Dexie):
  • PC -> threadsvault
  • Android -> threadsvault_android
• Active data space is persisted and restored between sessions.

Validation

• npm run build ✅
• cargo check ✅
• Manual E2E import test with real Android .json backup ✅
• Verified PC/Android dashboard toggle and data isolation ✅