Private personal product · Portable Windows application
Bibliothèque Bahith
A portable, offline-first Windows library for organising and reading Arabic PDF collections and downloaded audio or video lessons directly from external storage.
01
The challenge
Make a large research collection dependable on a removable disk whose drive letter can change, while keeping books, playback progress, settings, covers, logs, and recovery data on that disk.
02
My contribution
Across the product boundary.
- Built an Electron desktop application with Arabic-first navigation, French settings support, large-display modes, and an offline library experience.
- Implemented recursive PDF indexing, folder-based categories, search, favourites, reading progress, thumbnails, and an integrated reader.
- Designed portable relative-path handling, SQLite persistence, incremental rescans, backups, corruption recovery, and guarded file access.
- Implemented resumable content synchronisation and downloads for manuscripts and lesson media, with offline playback and progress continuation.
- Used AI-assisted development to accelerate exploration, implementation, testing, and documentation while validating behaviour in the source and release build.
03
System view
The parts that had to agree.
A generated portable Windows executable that can travel with its library, retain user state offline, recover its catalogue, and continue interrupted content downloads.
Electron, React, Vite, and TypeScript desktop shell
Portable SQLite catalogue with relative paths
PDF.js reader and thumbnail pipeline
File watching, incremental scanning, backups, and recovery
Resumable manuscript and lesson-media synchronisation
04
Visual evidence
Approved assets only.
No synthetic product UI is used. These slots document exactly what to capture when publication is authorised.
05
Evidence & boundaries
What can be verified.
- The private source, automated tests, portable-path design, README, and generated Bibliotheque.exe release were inspected locally.
- The executable was not launched during the portfolio audit; claims are bounded to source and release artefacts.
- The application and source remain private and no hosted URL is published.
Private desktop source and local content paths are not disclosed; only verified product behaviour is described.