How acreom/app works
• An Electron-based desktop application
• A web/mobile frontend built with Nuxt/Vue
• A Quick Capture module for fast input
All three share core business logic, storage, encryption, and synchronization capabilities, while also interacting with external services (calendars, issue trackers, etc.) via dedicated integration modules and worker processes.
Main Components
– UI Layers:
• Desktop UI (Electron): Contains the “electron” folder with its own app, window management, tray handling, drivers (for AI, calendar sync, attachments, etc.), and native integrations.
• Quick Capture: A specialized lightweight module (folder “quick-capture”) with its own components and support for fast note and task insertion.
– Core Business Logic & Data Management:
• Common data models for Pages, Tasks, Projects, Vaults, etc. These are shared between the Electron and Frontend modules.
• Local storage and syncing modules (including an IndexedDB-based layer found in “workers/database/indexeddb”).
• End-to-end encryption support and versioning.
– Integration & Sync Services:
• For external APIs: Apple/Google Calendar sync, Jira, GitHub, and Linear integrations (found in both “electron/driver” and “frontend/plugins/entities”, and further worker-based integrations under “workers/integrations”).
– Background Processes:
• Dedicated worker threads that handle tasks such as encryption, cloud syncing, markdown parsing (in “workers”), and AI assistant communications.
– Plugin & Service Layers:
• A structured plugin system exists in both the frontend (plugins folder) and electron (driver and helpers folders) that help in modularizing services such as notifications, shortcuts, service registry, context menus, etc.
Relationships and Data Flow
– The UI components communicate with local storage mechanisms (whether file system or IndexedDB) and invoke services (via plugins or drivers) to both process data and manage sync.
– Indicate the role of worker threads or processes (e.g. “workers/encryption”, “workers/database”, “workers/integrations”) in executing background tasks such as encryption, data synchronization, and processing markdown.
Architectural Patterns and Technologies
– Emphasize the separation between presentation (UI), business logic (data models, services, plugins), and data persistence (local stores like IndexedDB and file system integrations).
– Note the use of Electron as a hybrid container with its main and renderer processes, and the utilization of Nuxt/Vue for the web/mobile frontend.
– Mark the plugin architecture which allows for extensibility into integrations and background services.
– Identify use of TypeScript across modules, Node.js for backend scripts, and Yarn for package management.
– Indicate that many of the UI components are modularized (organized under “components”, “plugins”, “store”, etc.) to allow for reusability.