How divyanshunegi/capiq works
Project type and purpose
• This is a Turborepo-managed monorepo containing two primary applications:
• A cross-platform desktop application (“CapIQ Desktop”) built with Tauri (Rust backend) and React + TypeScript frontend, for automated photo/video organization.
• A static landing/marketing site (“CapIQ Web”) built with Next.js.
• The desktop app uses AI services to analyze media, organizes files locally, and presents a user interface in React. The web app is purely informational.
File structure
• Top level:
• pnpm-workspace.yaml & turbo.json → monorepo orchestration.
• apps/desktop → Tauri project (Cargo.toml, Rust code, React code under src/).
• apps/web → Next.js static site (pages under src/app, CSS, Tailwind).
• Desktop substructure:
• src-tauri/ → Rust backend: command definitions (lib.rs), main.rs, build.rs, capabilities JSON, auto-generated schemas.
• src/ → React app: components, hooks, stores, layouts, pages.
• configuration: vite.config.ts, Tailwind, ESLint, Prettier.
• No separate backend service outside Tauri; no external database server. State stored locally (via Tauri APIs).
• Other files: Gitignore, LICENSE, CONTRIBUTING, build logs under .turbo.
README for additional insights
• Confirms Tauri + React + TypeScript + TailwindCSS for the desktop app.
• Highlights AI integration for media analysis.
• Turborepo for local development with pnpm desktop and pnpm web commands.
Diagramming conventions
• UI → Bridge → Backend → File System
• Backend → AI Service (HTTP)
• Turborepo → Build processes for Desktop & Web
• Green rectangles for frontend UIs
• Blue rectangles for backends
Thoroughness
• Every component: monorepo, dev tools, CI/CD (if any), local vs. remote services.
• State flows: how media goes from disk → AI → storage → UI.
• Do not over-abstract: include the Tauri IPC layer, local store, AI API, frontend, and static site.