Feature and its Use Cases
A local backup system in the Settings page that allows users to export their locally cached invoice data to a JSON file and import it back into the app using IndexedDB (idb-backup).
- How would users benefit from it?
Since Chainvoice is transitioning to an architecture where sensitive invoice payloads (like client names and items) are no longer stored on-chain (only hashes are stored), users risk losing their invoice details if they clear their browser cache or switch devices. This feature gives users full ownership and control to backup their local data.
- What scenarios would this feature address?
- Transferring invoice history to a new browser or device.
- Safeguarding local data against accidental browser cache clearing.
- Restoring legacy or demo invoice data for testing purposes.
Additional Context
- The UI integrates into the existing Settings page, matching the current Chainvoice design language.
- Includes strict error handling and validation to ensure the uploaded JSON matches the Chainvoice schema before parsing and storing it.
- Safely integrates with the local cache indexes so that imported invoices immediately populate the Sent and Received tabs.
Code of Conduct
Feature and its Use Cases
A local backup system in the Settings page that allows users to export their locally cached invoice data to a JSON file and import it back into the app using IndexedDB (
idb-backup).Since Chainvoice is transitioning to an architecture where sensitive invoice payloads (like client names and items) are no longer stored on-chain (only hashes are stored), users risk losing their invoice details if they clear their browser cache or switch devices. This feature gives users full ownership and control to backup their local data.
Additional Context
Code of Conduct