The web app and PWA

The web app has the KDE app’s destinations, words, order and flows, so someone who uses one can use the other. It looks different: it uses the Verdure design language of parchment, forest, sage and gold.

• A desktop shell (Tauri) opens files and windows like the KDE app, with the same File menu.
• An installable PWA works offline and, once installed, can open .kabacus files from the file manager where the browser supports it.
• Books in a browser run the same libraries compiled to WebAssembly. Chromium saves back to the file you picked and asks once per file after a restart; other browsers keep the books in browser storage, and Save a Copy As… downloads them.
• One set of books per tab.
• A server can host the web app at /app/; it then opens that server’s books after sign-in.

Offline and storage boundaries

The PWA caches application assets, not server API responses or a backup of your books. Local books use the portable engine inside the page and write the whole file on save. A server outage does not turn shared books into an editable offline copy: loaded data stays readable and writes wait for reconnection without being queued.

After a Chromium restart, approve reopening the chosen file before editing. In other browsers, download a copy before clearing site storage. The desktop shell uses native file access and stores refresh tokens outside the JavaScript workspace; a browser session has different persistence rules.

• Save copies, back up and recover
• Keyboard shortcuts and languages