How mukeshsoni/vikara works
Project type and purpose
• This is a cross‐platform desktop application (“Vikara”) for image conversion.
• It uses Tauri as the shell: a Rust‐based backend (image processing) paired with a web frontend (React/TypeScript + Vite).
• The app loads images (JPEG, PNG, RAW, HEIC, etc.), applies transformations (resize, quality), and writes the converted file back to disk.
File structure
• Top level:
• index.html, public/, src/, package.json, vite.config.ts → front-end code & build
• src-tauri/ → Tauri Rust backend & configuration
• scripts/update_libs.js → updates bundled native image-codec libraries
• src/ (front-end): React/TypeScript components (App.tsx, main.tsx), CSS modules, constants and schema for the conversion form.
• src-tauri/src/ (backend):
• main.rs → Tauri event loop / command registration
• image_helpers.rs → business logic (invokes external image libs)
• lib.rs → shared modules or utility glue
• src-tauri/external-libs/: dynamic libraries for codecs (libheif, libdav1d, libx265, etc.).
• Configuration: tauri.conf.json, Cargo.toml, postcss.config.cjs, tsconfig.json.
README
• Confirms it’s an image‐conversion desktop app built with Tauri.
• Lists supported formats and a TODO to persist user settings via Tauri store.
Components & interactions
a. Main components:
1. UI Layer (React + Vite)
2. Tauri Runtime (IPC bridge)
3. Rust Backend (Tauri command handlers)
4. External Image Libraries (FFmpeg-style dynamic libs)
5. File System / OS (file dialogs, read/write)
6. (Future) Tauri Store for settings persistence
b. Relationships & data flow:
• User interacts with UI → selects files & parameters →
• UI issues Tauri.invoke(“convert_image”, payload) →
• Tauri runtime forwards to Rust main.rs →
• image_helpers.rs loads input file, calls external‐libs (libheif, libx265, etc.) →
• Generates output buffer/file → backend returns result (path/status) →
• UI receives result, displays success & writes file if needed.
c. Architectural patterns:
• Separation of concerns: UI (presentation) vs. Rust (business logic)
• IPC pattern (command/response) via Tauri
• Plugin-style external libs for codec support (dynamic linking)
d. Key technologies:
• React + Vite + TypeScript
• Tauri (Rust + WebView2 / WebKit)
• image_helpers.rs + native libs
• Node scripts for updating native libs
Additional details to capture
• Build artifacts: Vite dev server vs. production build.
• Configuration files (tauri.conf.json) influencing windowing & permissions.
• Script for native-lib updates (scripts/update_libs.js).
• Top: User & UI (React),
• Middle: Tauri IPC bridge,
• Bottom: Rust logic + external libs + file system,
• Side: Build & packaging pipeline.